V2X Supported Band Combination Sequence of a Wireless Device

ABSTRACT

A base station receives a first sequence of capability parameters from a wireless device. Each of the first sequence of capability parameters indicate whether a vehicle-to-everything (V2X) transmission is supported in a corresponding frequency band combination of a second sequence of frequency band combinations of the wireless device. The corresponding frequency band combination comprises one or more frequency band identifiers each indicating a specific frequency band. V2X configuration parameters of a cell operating in one of the frequency band combinations on which the wireless device supports the V2X transmission is transmitted.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Pat. No. 15/674,286, filedAug. 10, 2017, which claims the benefit of U.S. Provisional ApplicationNo. 62/373,254, filed Aug. 10, 2016 and U.S. Provisional Application No.62/374,803, filed Aug. 13, 2016, which are hereby incorporated byreference in their entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present disclosure.

FIG. 3 is an example diagram depicting OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 4 is an example block diagram of a base station and a wirelessdevice as per an aspect of an embodiment of the present disclosure.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 6 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure.

FIG. 10 is an example diagram depicting Activation/Deactivation MACcontrol elements as per an aspect of an embodiment of the presentdisclosure.

FIG. 11 is an example diagram depicting example subframe offset valuesas per an aspect of an embodiment of the present disclosure.

FIG. 12 is an example diagram depicting example uplink SPS activationand release as per an aspect of an embodiment of the present disclosure.

FIG. 13 is an example diagram depicting example multiple parallel SPSsas per an aspect of an embodiment of the present disclosure.

FIG. 14 is an example diagram depicting example RRC configuration andexample DCIs as per an aspect of an embodiment of the presentdisclosure.

FIG. 15 is an example diagram depicting example RRC configuration andexample DCIs as per an aspect of an embodiment of the presentdisclosure.

FIG. 16 is an example diagram depicting example DCIs as per an aspect ofan embodiment of the present disclosure.

FIG. 17 is an example diagram depicting example signaling flow as per anaspect of an embodiment of the present disclosure.

FIG. 18 is an example diagram depicting example signaling flow as per anaspect of an embodiment of the present disclosure.

FIG. 19 is an example diagram depicting example UE V2X capabilities asper an aspect of an embodiment of the present disclosure.

FIG. 20 is an example diagram depicting example UE V2X capabilities asper an aspect of an embodiment of the present disclosure.

FIG. 21 is an example diagram depicting example UE V2X capabilities asper an aspect of an embodiment of the present disclosure.

FIG. 22 is an example diagram depicting example network providing V2Xservices as per an aspect of an embodiment of the present disclosure.

FIG. 23 is an example diagram depicting example signaling flow as per anaspect of an embodiment of the present disclosure.

FIG. 24 is an example diagram depicting example signaling flow as per anaspect of an embodiment of the present disclosure.

FIG. 25 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 26 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 27 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 28 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 29 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

FIG. 30 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation ofcarrier aggregation. Embodiments of the technology disclosed herein maybe employed in the technical field of multicarrier communicationsystems.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit BPSK binary phase shiftkeying CA carrier aggregation CSI channel state information CDMA codedivision multiple access CSS common search space CPLD complexprogrammable logic devices CC component carrier DL downlink DCI downlinkcontrol information DC dual connectivity EPC evolved packet core E-UTRANevolved-universal terrestrial radio access network FPGA fieldprogrammable gate arrays FDD frequency division multiplexing HDLhardware description languages HARQ hybrid automatic repeat request IEinformation element LAA licensed assisted access LTE long term evolutionMCG master cell group MeNB master evolved node B MIB master informationblock MAC media access control MAC media access control MME mobilitymanagement entity NAS non-access stratum OFDM orthogonal frequencydivision multiplexing PDCP packet data convergence protocol PDU packetdata unit PHY physical PDCCH physical downlink control channel PHICHphysical HARQ indicator channel PUCCH physical uplink control channelPUSCH physical uplink shared channel PCell primary cell PCell primarycell PCC primary component carrier PSCell primary secondary cell pTAGprimary timing advance group QAM quadrature amplitude modulation QPSKquadrature phase shift keying RBG Resource Block Groups RLC radio linkcontrol RRC radio resource control RA random access RB resource blocksSCC secondary component carrier SCell secondary cell Scell secondarycells SCG secondary cell group SeNB secondary evolved node B sTAGssecondary timing advance group SDU service data unit S-GW servinggateway SRB signaling radio bearer SC-OFDM single carrier-OFDM SFNsystem frame number SIB system information block TAI tracking areaidentifier TAT time alignment timer TDD time division duplexing TDMAtime division multiple access TA timing advance TAG timing advance groupTB transport block UL uplink UE user equipment VHDL VHSIC hardwaredescription language

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, the radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as 0.5 msec, 1 msec,2 msec, and 5 msec may also be supported. Subframe(s) may consist of twoor more slots (for example, slots 206 and 207). For the example of FDD,10 subframes may be available for downlink transmission and 10 subframesmay be available for uplink transmissions in each 10 ms interval. Uplinkand downlink transmissions may be separated in the frequency domain.Slot(s) may include a plurality of OFDM symbols 203. The number of OFDMsymbols 203 in a slot 206 may depend on the cyclic prefix length andsubcarrier spacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs (in this example 6 to 100 RBs) may depend,at least in part, on the downlink transmission bandwidth 306 configuredin the cell. The smallest radio resource unit may be called a resourceelement (e.g. 301). Resource elements may be grouped into resourceblocks (e.g. 302). Resource blocks may be grouped into larger radioresources called Resource Block Groups (RBG) (e.g. 303). The transmittedsignal in slot 206 may be described by one or several resource grids ofa plurality of subcarriers and a plurality of OFDM symbols. Resourceblocks may be used to describe the mapping of certain physical channelsto resource elements. Other pre-defined groupings of physical resourceelements may be implemented in the system depending on the radiotechnology. For example, 24 subcarriers may be grouped as a radio blockfor a duration of 5 msec. In an illustrative example, a resource blockmay correspond to one slot in the time domain and 180 kHz in thefrequency domain (for 15 KHz subcarrier bandwidth and 12 subcarriers).

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 5A shows an example uplink physicalchannel. The baseband signal representing the physical uplink sharedchannel may perform the following processes. These functions areillustrated as examples and it is anticipated that other mechanisms maybe implemented in various embodiments. The functions may comprisescrambling, modulation of scrambled bits to generate complex-valuedsymbols, mapping of the complex-valued modulation symbols onto one orseveral transmission layers, transform precoding to generatecomplex-valued symbols, precoding of the complex-valued symbols, mappingof precoded complex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for each antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in each ofthe codewords to be transmitted on a physical channel; modulation ofscrambled bits to generate complex-valued modulation symbols; mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on each layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for each antenna port to resource elements;generation of complex-valued time-domain OFDM signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present disclosure.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to aspects of an embodiments, transceiver(s) may be employed.A transceiver is a device that includes both a transmitter and receiver.Transceivers may be employed in devices such as wireless devices, basestations, relay nodes, and/or the like. Example embodiments for radiotechnology implemented in communication interface 402, 407 and wirelesslink 411 are illustrated are FIG. 1, FIG. 2, FIG. 3, FIG. 5, andassociated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to various aspects of an embodiment, an LTE network mayinclude a multitude of base stations, providing a user planePDCP/RLC/MAC/PHY and control plane (RRC) protocol terminations towardsthe wireless device. The base station(s) may be interconnected withother base station(s) (for example, interconnected employing an X2interface). Base stations may also be connected employing, for example,an S1 interface to an EPC. For example, base stations may beinterconnected to the MME employing the S1-MME interface and to the S-G)employing the S1-U interface. The S1 interface may support amany-to-many relation between MMEs/Serving Gateways and base stations. Abase station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink,the carrier corresponding to the PCell may be the Uplink PrimaryComponent Carrier (UL PCC). Depending on wireless device capabilities,Secondary Cells (SCells) may be configured to form together with thePCell a set of serving cells. In the downlink, the carrier correspondingto an SCell may be a Downlink Secondary Component Carrier (DL SCC),while in the uplink, it may be an Uplink Secondary Component Carrier (ULSCC). An SCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may apply,for example, to carrier activation. When the specification indicatesthat a first carrier is activated, the specification may also mean thatthe cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE release with agiven capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTEtechnology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand DC as per an aspect of an embodiment of the present disclosure.E-UTRAN may support Dual Connectivity (DC) operation whereby a multipleRX/TX UE in RRC CONNECTED may be configured to utilize radio resourcesprovided by two schedulers located in two eNBs connected via a non-idealbackhaul over the X2 interface. eNBs involved in DC for a certain UE mayassume two different roles: an eNB may either act as an MeNB or as anSeNB. In DC a UE may be connected to one MeNB and one SeNB. Mechanismsimplemented in DC may be extended to cover more than two eNBs. FIG. 7illustrates one example structure for the UE side MAC entities when aMaster Cell Group (MCG) and a Secondary Cell Group (SCG) are configured,and it may not restrict implementation. Media Broadcast MulticastService (MBMS) reception is not shown in this figure for simplicity.

In DC, the radio protocol architecture that a particular bearer uses maydepend on how the bearer is setup. Three alternatives may exist, an MCGbearer, an SCG bearer and a split bearer as shown in FIG. 6. RRC may belocated in MeNB and SRBs may be configured as a MCG bearer type and mayuse the radio resources of the MeNB. DC may also be described as havingat least one bearer configured to use radio resources provided by theSeNB. DC may or may not be configured/implemented in example embodimentsof the disclosure.

In the case of DC, the UE may be configured with two MAC entities: oneMAC entity for MeNB, and one MAC entity for SeNB. In DC, the configuredset of serving cells for a UE may comprise two subsets: the Master CellGroup (MCG) containing the serving cells of the MeNB, and the SecondaryCell Group (SCG) containing the serving cells of the SeNB. For a SCG,one or more of the following may be applied. At least one cell in theSCG may have a configured UL CC and one of them, named PSCell (or PCellof SCG, or sometimes called PCell), may be configured with PUCCHresources. When the SCG is configured, there may be at least one SCGbearer or one Split bearer. Upon detection of a physical layer problemor a random access problem on a PSCell, or the maximum number of RLCretransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG may be stopped, anda MeNB may be informed by the UE of a SCG failure type. For splitbearer, the DL data transfer over the MeNB may be maintained. The RLC AMbearer may be configured for the split bearer. Like a PCell, a PSCellmay not be de-activated. A PSCell may be changed with a SCG change (forexample, with a security key change and a RACH procedure), and/orneither a direct bearer type change between a Split bearer and a SCGbearer nor simultaneous configuration of a SCG and a Split bearer may besupported.

With respect to the interaction between a MeNB and a SeNB, one or moreof the following principles may be applied. The MeNB may maintain theRRM measurement configuration of the UE and may, (for example, based onreceived measurement reports or traffic conditions or bearer types),decide to ask a SeNB to provide additional resources (serving cells) fora UE. Upon receiving a request from the MeNB, a SeNB may create acontainer that may result in the configuration of additional servingcells for the UE (or decide that it has no resource available to do so).For UE capability coordination, the MeNB may provide (part of) the ASconfiguration and the UE capabilities to the SeNB. The MeNB and the SeNBmay exchange information about a UE configuration by employing RRCcontainers (inter-node messages) carried in X2 messages. The SeNB mayinitiate a reconfiguration of its existing serving cells (for example, aPUCCH towards the SeNB). The SeNB may decide which cell is the PSCellwithin the SCG. The MeNB may not change the content of the RRCconfiguration provided by the SeNB. In the case of a SCG addition and aSCG SCell addition, the MeNB may provide the latest measurement resultsfor the SCG cell(s). Both a MeNB and a SeNB may know the SFN andsubframe offset of each other by OAM, (for example, for the purpose ofDRX alignment and identification of a measurement gap). In an example,when adding a new SCG SCell, dedicated RRC signaling may be used forsending required system information of the cell as for CA, except forthe SFN acquired from a MIB of the PSCell of a SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure. In Example 1, pTAG comprises aPCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises aPCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3,pTAG comprises PCell and SCell1, and an sTAG1 includes SCell2 andSCell3, and sTAG2 comprises SCell4. Up to four TAGs may be supported ina cell group (MCG or SCG) and other example TAG configurations may alsobe provided. In various examples in this disclosure, example mechanismsare described for a pTAG and an sTAG. Some of the example mechanisms maybe applied to configurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure. An eNB transmits an activation command 600 to activate anSCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCHorder 601 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 603 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 604 may betransmitted on the SCell in which the preamble was transmitted.

According to an embodiment, initial timing alignment may be achievedthrough a random access procedure. This may involve a UE transmitting arandom access preamble and an eNB responding with an initial TA commandNTA (amount of timing advance) within a random access response window.The start of the random access preamble may be aligned with the start ofa corresponding uplink subframe at the UE assuming NTA=0. The eNB mayestimate the uplink timing from the random access preamble transmittedby the UE. The TA command may be derived by the eNB based on theestimation of the difference between the desired UL timing and theactual UL timing. The UE may determine the initial uplink transmissiontiming relative to the corresponding downlink of the sTAG on which thepreamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to variousaspects of an embodiment, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding(configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, (for example, at least one RRC reconfigurationmessage), may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of thepTAG. Wwhen an SCell is added/configured without a TAG index, the SCellmay be explicitly assigned to the pTAG. The PCell may not change its TAgroup and may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (for example, to establish, modify and/orrelease RBs, to perform handover, to setup, modify, and/or releasemeasurements, to add, modify, and/or release SCells). If the receivedRRC Connection Reconfiguration message includes the sCellToReleaseList,the UE may perform an SCell release. If the received RRC ConnectionReconfiguration message includes the sCellToAddModList, the UE mayperform SCell additions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH may only be transmitted onthe PCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. In the example embodiments, one, two or more cellsmay be configured with PUCCH resources for transmitting CSI/ACK/NACK toa base station. Cells may be grouped into multiple PUCCH groups, and oneor more cell within a group may be configured with a PUCCH. In anexample configuration, one SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/orif theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the disclosure may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

In an example, the MAC entity may be configured with one or more SCells.In an example, the network may activate and/or deactivate the configuredSCells. The SpCell may always be activated. The network may activate anddeactivates the SCell(s) by sending the Activation/Deactivation MACcontrol element. The MAC entity may maintain a sCellDeactivationTimertimer for a configured SCell. Upon the expiry of sCellDeactivationTimertimer, the MAC entity may deactivate the associated SCell. In anexample, the same initial timer value may apply to each instance of thesCellDeactivationTimer and it may be configured by RRC. The configuredSCells may initially be deactivated upon addition and after a handover.The configured SCG SCells may initially be deactivated after a SCGchange.

In an example, if the MAC entity receives an Activation/Deactivation MACcontrol element in a TTI activating a SCell, the MAC entity may, in aTTI according to the timing defined below, activate the SCell and applynormal SCell operation including SRS transmissions on the SCell,CQI/PMI/RI/PTI/CRI reporting for the SCell, PDCCH monitoring on theSCell, PDCCH monitoring for the SCell and PUCCH transmissions on theSCell, if configured. The MAC entity may start or restart thesCellDeactivationTimer associated with the SCell and trigger powerheadroom report (PHR). In an example, if the MAC entity receives anActivation/Deactivation MAC control element in a TTI deactivating aSCell or if the sCellDeactivationTimer associated with an activatedSCell expires in the TTI, the MAC entity may, in a TTI according to thetiming defined below, deactivate the SCell, stop thesCellDeactivationTimer associated with the SCell and flush all HARQbuffers associated with the SCell.

In an example, when a UE receives an activation command for a secondarycell in subframe n, the corresponding actions above may be applied nolater than the minimum requirements and no earlier than subframe n+8,except for the actions related to CSI reporting on a serving cell whichmay be active in subframe n+8 and the actions related to thesCellDeactivationTimer associated with the secondary cell which may beapplied in subframe n+8. The actions related to CSI reporting on aserving cell which is not active in subframe n+8 may be applied in theearliest subframe after n+8 in which the serving cell is active.

In an example, when a UE receives a deactivation command for a secondarycell or the sCellDeactivationTimer associated with the secondary cellexpires in subframe n, the corresponding actions above may apply nolater than the minimum requirement except for the actions related to CSIreporting on a serving cell which is active which may be applied insubframe n+8.

In an example, if the PDCCH on the activated SCell indicates an uplinkgrant or downlink assignment or if the PDCCH on the Serving Cellscheduling an activated SCell indicates an uplink grant or a downlinkassignment for the activated SCell, the MAC entity may restart thesCellDeactivationTimer associated with the SCell.

In an example, if a SCell is deactivated, the UE may not transmit SRS onthe SCell, may not report CQI/PMI/RI/PTI/CRI for the SCell, may nottransmit on UL-SCH on the SCell, may not transmit on RACH on the SCell,may not monitor the PDCCH on the SCell, may not monitor the PDCCH forthe SCell and may not transmit PUCCH on the SCell.

In an example, the HARQ feedback for the MAC PDU containingActivation/Deactivation MAC control element may not be impacted by PCellinterruption due to SCell activation/deactivation. In an example, whenSCell is deactivated, the ongoing Random Access procedure on the SCell,if any, may be aborted.

In an example, the Activation/Deactivation MAC control element of oneoctet may be identified by a MAC PDU subheader with LCID 11000. FIG. 10shows example Activation/Deactivation MAC control elements. TheActivation/Deactivation MAC control element may have a fixed size andmay consist of a single octet containing seven C-fields and one R-field.Example Activation/Deactivation MAC control element with one octet isshown in FIG. 10. The Activation/Deactivation MAC control element mayhave a fixed size and may consist of four octets containing 31 C-fieldsand one R-field. Example Activation/Deactivation MAC control element offour octets is shown in FIG. 10. In an example, for the case with noserving cell with a serving cell index (ServCellIndex) larger than 7,Activation/Deactivation MAC control element of one octet may be applied,otherwise Activation/Deactivation MAC control element of four octets maybe applied. The fields in an Activation/Deactivation MAC control elementmay be interpreted as follows. Ci: if there is an SCell configured withSCellIndex i, this field may indicate the activation/deactivation statusof the SCell with SCellIndex i, else the MAC entity may ignore the Cifield. The Ci field may be set to “1” to indicate that the SCell withSCellIndex i is activated. The Ci field is set to “0” to indicate thatthe SCell with SCellIndex i is deactivated. R: Reserved bit, set to “0”.

A base station may provide a periodic resource allocation. In a periodicresource allocation, an RRC message and/or a DCI may activate or releasea periodic resource allocation. The UE may be allocated in downlinkand/or uplink periodic radio resources without the need for transmissionof additional grants by the base station. The periodic resourceallocation may remain activated until it is released. The periodicresource allocation for example, may be called, semi-persistentscheduling or grant-free scheduling, or periodic multi-subframescheduling, and/or the like. In this specification, the example termsemi-persistent scheduling is mostly used, but other terms may also beequally used to refer to periodic resource allocation, e.g. grant-freescheduling. An example periodic resource allocation activation andrelease is shown in FIG. 12.

In the downlink, a base station may dynamically allocate resources (PRBsand MCS) to UEs at a TTI via the C-RNTI on PDCCH(s). A UE may monitorthe PDCCH(s) in order to find possible allocation when its downlinkreception is enabled (e.g. activity governed by DRX when configured).When CA is configured, the same C-RNTI applies to serving cells. Basestation may also allocate semi-persistent downlink resources for thefirst HARQ transmissions to UEs. In an example, an RRC message mayindicate the periodicity of the semi-persistent downlink grant. In anexample, a PDCCH DCI may indicate whether the downlink grant is asemi-persistent one e.g. whether it can be implicitly reused in thefollowing TTIs according to the periodicity defined by RRC.

In an example, when required, retransmissions may be explicitly signaledvia the PDCCH(s). In the sub-frames where the UE has semi-persistentdownlink resource, if the UE cannot find its C-RNTI on the PDCCH(s), adownlink transmission according to the semi-persistent allocation thatthe UE has been assigned in the TTI is assumed. Otherwise, in thesub-frames where the UE has semi-persistent downlink resource, if the UEfinds its C-RNTI on the PDCCH(s), the PDCCH allocation may override thesemi-persistent allocation for that TTI and the UE may not decode thesemi-persistent resources.

When CA is configured, semi-persistent downlink resources may beconfigured for the PCell and/or SCell(s). In an example, PDCCH dynamicallocations for the PCell and/or SCell(s) may override thesemi-persistent allocation.

In the uplink, a base station may dynamically allocate resources (PRBsand MCS) to UEs at a TTI via the C-RNTI on PDCCH(s). A UE may monitorthe PDCCH(s) in order to find possible allocation for uplinktransmission when its downlink reception is enabled (activity governedby DRX when configured). When CA is configured, the same C-RNTI appliesto serving cells. In addition, a base station may allocate asemi-persistent uplink resource for the first HARQ transmissions andpotentially retransmissions to UEs. In an example, an RRC may define theperiodicity of the semi-persistent uplink grant. PDCCH may indicatewhether the uplink grant is a semi-persistent one e.g. whether it can beimplicitly reused in the following TTIs according to the periodicitydefined by RRC.

In an example, in the sub-frames where the UE has semi-persistent uplinkresource, if the UE cannot find its C-RNTI on the PDCCH(s), an uplinktransmission according to the semi-persistent allocation that the UE hasbeen assigned in the TTI may be made. The network may perform decodingof the pre-defined PRBs according to the pre-defined MCS. Otherwise, inthe sub-frames where the UE has semi-persistent uplink resource, if theUE finds its C-RNTI on the PDCCH(s), the PDCCH allocation may overridethe persistent allocation for that TTI and the UE's transmission followsthe PDCCH allocation, not the semi-persistent allocation.Retransmissions may be either implicitly allocated in which case the UEuses the semi-persistent uplink allocation, or explicitly allocated viaPDCCH(s) in which case the UE does not follow the semi-persistentallocation.

Vehicular communication services, represented by V2X services, maycomprise of the following different types: V2V, V2I, V2N and/or V2P. V2Xservices may be provided by PC5 interface (sidelink) and/or Uu interface(UE to base station interface). Support of V2X services via PC5interface may be provided by V2X sidelink communication, which is a modeof communication whereby UEs may communicate with each other directlyover the PC5 interface. This communication mode may be supported whenthe UE is served by E-UTRAN and when the UE is outside of E-UTRAcoverage. The UEs authorized to be used for V2X services may perform V2Xsidelink communication.

The user plane protocol stack and functions for sidelink communicationmay be used for V2X sidelink communication. In order to assist the eNBto provide sidelink resources, the UE in RRC CONNECTED may reportgeographical location information to the eNB. The eNB may configure theUE to report the complete UE geographical location information based onperiodic reporting via the existing measurement report signaling.

In an example, for V2X communication, k SPS (e.g. k=8 or 16, etc)configurations with different parameters may be configured by eNB andSPS configurations may be active at the same time. Theactivation/deactivation of an SPS configuration may signaled via a PDCCHDCI and/or an RRC message by eNB. The logical channel prioritization forUu may be used.

For V2X communication, a UE may provide UE assistance information to aneNB. Reporting of UE assistance information may be configured by eNBtransmitting one or more RRC messages. The UE assistance information mayinclude parameters related to the SPS configuration. Triggering of UEassistance information transmission may be left to UE implementation.For instance, the UE may be allowed to report the UE assistanceinformation when change in estimated periodicity and/or timing offset ofpacket arrival occurs. For V2X communication via Uu, SR mask as perlegacy mechanism may be used.

In an example, for unicast transmission of V2X messages, the V2X messagemay be delivered via Non-GBR bearers as well as GBR bearers. In order tomeet the QoS requirement for V2X message delivery for V2X services, aNon-GBR QCI value and a GBR QCI value for V2X messages may be used. Forbroadcasting V2X messages, SC-PTM or MBSFN transmission may be used. Inorder to reduce SC-PTM/MBSFN latency, shorter (SC-)MCCH repetitionperiod for SC-PTM/MBSFN, modification period for SC-PTM/MBSFN and MCHscheduling period for MBSFN may be supported. Reception of downlinkbroadcast of V2X messages in different carriers/PLMNs may be supportedby having multiple receiver chains in the UE.

In an example embodiment, various DCI formats may be used for SPSscheduling. For example, the DCI format 0 may be used for uplink SPS. Inan example, the fields for DCI format 0 may comprise one or more of thefollowing fields: Carrier indicator e.g. 0 or 3 bits. Flag forformat0/format1A differentiation e.g. 1 bit, where value 0 may indicateformat 0 and value 1 may indicate format 1A. Frequency hopping flag,e.g. 1 bit. This field may be used as the MSB of the correspondingresource allocation for resource allocation type 1. Resource blockassignment and hopping resource allocation, e.g. clog ┌log ₂(N_(RB)^(UL)(N_(RB) ^(UL)+1)┐ bits where N_(RB) ^(UL) may be the uplinkbandwidth configuration in number of resource blocks. Modulation andcoding scheme and redundancy version e.g. 5 bits. New data indicatore.g. 1 bit. TPC command for scheduled PUSCH e.g. 2 bits. Cyclic shiftfor DM RS and OCC index e.g. 3 bits. UL index e.g. 2 bits (this fieldmay be present for TDD operation with uplink-downlink configuration 0).Downlink Assignment Index (DAI) e.g. 2 bits (this field may be presentfor cases with TDD primary cell and either TDD operation withuplink-downlink configurations 1-6 or FDD operation). CSI request e.g.1, 2 or 3 bits. The 2-bit field may apply to UEs configured with no morethan five DL cells and to UEs that are configured with more than one DLcell and when the corresponding DCI format is mapped onto the UEspecific search space given by the C-RNTI, UEs that are configured byhigher layers with more than one CSI process and when the correspondingDCI format is mapped onto the UE specific search space given by theC-RNTI, UEs that are configured with two CSI measurement sets by higherlayers with the parameter csi-MeasSubframeSet, and when thecorresponding DCI format is mapped onto the UE specific search spacegiven by the C-RNTI; the 3-bit field may apply to the UEs that areconfigured with more than five DL cells and when the corresponding DCIformat is mapped onto the UE specific search space given by the C-RNTI;otherwise the 1-bit field may apply. SRS request e.g. 0 or 1 bit. Thisfield may be present in DCI formats scheduling PUSCH which are mappedonto the UE specific search space given by the C-RNTI. Resourceallocation type e.g. 1 bit. This field may be present if N_(RB)^(UL)≤N_(RB) ^(DL) where N_(RB) ^(UL) may be the uplink bandwidthconfiguration in number of resource blocks and Na may be the downlinkbandwidth configuration in number of resource blocks. In example, one ormore fields may be added to a DCI for SPS to enhance SPS schedulingprocess. In example, one or more of the fields may be replaced with newfields, or new values, or may be interpreted differently for SPS toenhance SPS scheduling process.

A base station may transmit one or more RRC messages to a wirelessdevice to configure SPS. The one or more RRC messages may comprise SPSconfiguration parameters. Example SPS configuration parameters arepresented below. In example, one or more parameters may be added to anRRC message for SPS to enhance SPS scheduling process. In example, oneor more some of the parameters for an SPS in an RRC message may bereplaced with new parameters, or new values, or may be interpreteddifferently for SPS to enhance SPS scheduling process. In an example, IESPS-Config may be used by RRC to specify the semi-persistent schedulingconfiguration. In an example, the IE SPS-Config may be SEQUENCE{semiPersistSchedC-RNTI: C-RNTI; sps-ConfigDL: SPS-ConfigDL;sps-ConfigUL: SPS-ConfigUL}. SPS-ConfigDL IE may comprisesemiPersistSchedIntervalDL, numberOfConfSPS-Processes,n1PUCCH-AN-PersistentList, twoAntennaPortActivated,n1PUCCH-AN-PersistentListP1, and/or other parameters. In an example,SPS-ConfigUL IE may comprise semiPersistSchedIntervalUL,implicitReleaseAfter, p0-NominalPUSCH-Persistent,p0-UE-PUSCH-Persistent, twolntervalsConfig, p0-PersistentSubframeSet2,p0-NominalPUSCH-PersistentSubframeSet2, p0-UE-PUSCH-and/orPersistentSubframeSet2, and/or other parameters.

In an example, one or more RRC configuration parameters may comprise oneor more of the following parameters to configure SPS for a wirelessdevice. In an example, SPS configuration may include MCS employed forpacket transmission of an MCS grant. In an example, implicitReleaseAfterIE may be the number of empty transmissions before implicit release,e.g. value e2 may corresponds to 2 transmissions, e3 may correspond to 3transmissions and so on. In an example, n1PUCCH-AN-PersistentList IE,n1PUCCH-AN-PersistentListP1 IE may be the List of parameter: n_(PUCCH)^((1,p)) for antenna port P0 and for antenna port P1 respectively. Fieldn1-PUCCH-AN-PersistentListP1 IE may be applicable if thetwoAntennaPortActivatedPUCCH-Format1alb in PUCCH-ConfigDedicated-v1020is set to true. Otherwise the field may not be configured.

In an example, numberOfConfSPS-Processes IE may be the number ofconfigured HARQ processes for Semi-Persistent Scheduling. In an example,p0-NominalPUSCH-Persistent IE may be the parameter: P_(o_NOMINAL_ PUSCH)(0) used in PUSCH power control with unit in dBm and step 1. This fieldmay be applicable for persistent scheduling. If choice setup is used andp0-Persistent is absent, the value of p0-NominalPUSCH forp0-NominalPUSCH-Persistent may be applied. If uplink power controlsubframe sets are configured by tpc-SubframeSet, this field may applyfor uplink power control subframe set 1.

In an example, p0-NominalPUSCH-PersistentSubframeSet2 IE may be theparameter: P_(O_NOMINAL_ PUSCH) (0) used in PUSCH power control withunit in dBm and step 1. This field may be applicable for persistentscheduling. If p0-PersistentSubframeSet2-r12 is not configured, thevalue of p0-NominalPUSCH-SubframeSet2-r12 may be applied forp0-NominalPUSCH-PersistentSubframeSet2. E-UTRAN may configure this fieldif uplink power control subframe sets are configured by tpc-SubframeSet,in which case this field may apply for uplink power control subframe set2. In an example, p0-UE-PUSCH-Persistent IE may be the parameter:P_(O_UE_PUSCH)) (0) used in PUSCH power control with unit in dB. Thisfield may be applicable for persistent scheduling. If choice setup isused and p0-Persistent is absent, the value of p0-UE-PUSCH may beapplied for p0-UE-PUSCH-Persistent. If uplink power control subframesets are configured by tpc-SubframeSet, this field may be applied foruplink power control subframe set 1. In an example,p0-UE-PUSCH-PersistentSubframeSet2 IE may be the parameter:P_(O_UE_PUSCH)) (0) used in PUSCH power control with unit in dB. Thisfield may be applicable for persistent scheduling. Ifp0-PersistentSubframeSet2-r12 is not configured, the value ofp0-UE-PUSCH-SubframeSet2 may be applied forp0-UE-PUSCH-PersistentSubframeSet2. E-UTRAN may configure this field ifuplink power control subframe sets are configured by tpc-SubframeSet, inwhich case this field may apply for uplink power control subframe set 2.

In an example, semiPersistSchedC-RNTI IE may be Semi-PersistentScheduling C-RNTI. In an example, semiPersistSchedIntervalDL IE may beSemi-persistent scheduling interval in downlink. Its value may be innumber of sub-frames. Value sf10 may correspond to 10 sub-frames, sf20may correspond to 20 sub-frames and so on. For TDD, the UE may roundthis parameter down to the nearest integer (of 10 sub-frames), e.g. sf10may correspond to 10 sub-frames, sf32 may correspond to 30 sub-frames,sf128 may correspond to 120 sub-frames. In an example,semiPersistSchedIntervalUL IE may be semi-persistent scheduling intervalin uplink. Its value in number of sub-frames. Value sf10 may correspondto 10 sub-frames, sf20 may correspond to 20 sub-frames and so on. ForTDD, the UE may round this parameter down to the nearest integer (of 10sub-frames), e.g. sf10 may correspond to 10 sub-frames, sf32 maycorrespond to 30 sub-frames, sf128 may correspond to 120 sub-frames. Inan example, twoIntervalsConfig IE may be trigger oftwo-intervals-Semi-Persistent Scheduling in uplink. If this field ispresent, two-intervals-SPS is enabled for uplink. Otherwise,two-intervals-SPS is disabled.

In an example, multiple downlink or uplink SPS may be configured for acell. In an example, multiple SPS RNTIs may be configured when aplurality of SPSs is configured. A base station may transmit to a UE atleast one RRC message comprising SPS configuration parameters comprisinga first SPS RNTI and a second SPS RNTI. For example, a first SPS RNTImay be configured for a first SPS configuration (e.g. for VOIP), and asecond SPS RNTI may be configured for a second SPS configuration (e.g.for V2X communications). The UE may monitor PDCCH for at least DCIscorresponding to the first SPS RNTI and the second SPS RNTI.

When Semi-Persistent Scheduling is enabled by RRC, at least one or moreof the following information may be provided: Semi-Persistent SchedulingC-RNTI(s); Uplink Semi-Persistent Scheduling intervalsemiPersistSchedIntervalUL, number of empty transmissions beforeimplicit release implicitReleaseAfter, if Semi-Persistent Scheduling isenabled for the uplink; Whether twoIntervalsConfig is enabled ordisabled for uplink, for TDD; Downlink Semi-Persistent Schedulinginterval semiPersistSchedIntervalDL and number of configured HARQprocesses for Semi-Persistent Scheduling numberOfConfSPS-Processes, ifSemi-Persistent Scheduling is enabled for the downlink; and/or otherparameters.

When Semi-Persistent Scheduling for uplink or downlink is disabled byRRC, the corresponding configured grant or configured assignment may bediscarded.

In an example, after a Semi-Persistent downlink assignment isconfigured, the MAC entity may consider sequentially that the Nthassignment occurs in the subframe for which: (10* SFN+subframe)=[(10*SFNstart time+subframestart time)+N* semiPersistSchedIntervalDL] modulo10240. Where SFNstart time and subframestart time may be the SFN andsubframe, respectively, at the time the configured downlink assignmentwere (re)initialized.

In an example, after a Semi-Persistent Scheduling uplink grant isconfigured, the MAC entity may: if twoIntervalsConfig is enabled byupper layer: set the Subframe_Offset according to Table below. else: setSubframe_Offset to 0. consider sequentially that the Nth grant occurs inthe subframe for which: (10*SFN+subframe)=[(10* SFNstarttime+subframestart time)+N*semiPersistSchedIntervalUL+Subframe_Offset*(N modulo 2)] modulo 10240.Where

SFNstart time and subframestart time may be the SFN and subframe,respectively, at the time the configured uplink grant were(re-)initialised. FIG. 11. shows example subframe offset values.

The MAC entity may clear the configured uplink grant immediately afterimplicitReleaseAfter number of consecutive MAC PDUs containing zero MACSDUs have been provided by the Multiplexing and Assembly entity, on theSemi-Persistent Scheduling resource. Retransmissions for Semi-PersistentScheduling may continue after clearing the configured uplink grant.

In an example embodiment, SPS configurations may be enhanced to supporttransmission of various V2X traffic and/or voice traffic by a UE. Thereis a need to support multiple SPS configurations for a UE. For example,a UE supporting V2X may need to support multiple uplink SPSconfigurations for transmitting various periodic (or semi-periodic)traffic and/or voice traffic in the uplink. Other examples may beprovided. For example, CAM messages in V2X may be semi-periodic. In somescenarios, CAM message generation may be dynamic in terms of size,periodicity and timing. Such changes may result in misalignment betweenSPS timing and CAM timing. There may be some regularity in size andperiodicity between different triggers. Enhanced SPS mechanisms may bebeneficial to transmit V2X traffic, voice traffic, and/or the like. Inan example, various SPS periodicity, for example 100 ms and is may beconfigured.

In an example, multiple SPS configurations may be configured for UUand/or PC5 interface. An eNB may configure multiple SPS configurationsfor a given UE. In an example, SPS configuration specific MCS (e.g. MCSas a part of the RRC SPS-configuration) and/orSPS-configuration-specific periodicity may be configured. In an example,some of the SPS configuration parameters may be the same across multipleSPS and some other SPS configuration parameters may be different acrossSPS configurations. The eNB may dynamically trigger/release thedifferent SPS-configurations employing (E)PDCCH DCIs. In an example, themultiple SPS configurations may be indicated by eNB RRC signaling. Thedynamical triggering and releasing may be performed by eNB transmitting(E)PDCCH DCI to the UE employing SPS C-RNTI.

In an example embodiment, a UE may transmit UE SPS assistant informationto a base station indicating that the UE does not intend and/or intendto transmit data before a transmission associated to an SPSconfiguration. The eNB may acknowledge the UE indication. For V2Xcommunication, a UE may provide UE assistance information to an eNB.Reporting of UE assistance information may be configured by eNBtransmitting one or more RRC messages. The UE assistance information mayinclude parameters related to the SPS configuration. Triggering of UEassistance information transmission may be left to UE implementation.For instance, the UE may be allowed to report the UE assistanceinformation when change in estimated periodicity and/or timing offset ofpacket arrival occurs. For V2X communication via Uu, SR mask as perlegacy mechanism may be used.

Some example V2X messages are CAM, DENM and BSM. For Example, CAMmessage may have the following characteristics. Content: status (e.g.time, position, motion state, activated system), attribute (data aboutdimension, vehicle type and role in the road traffic). Periodicity:typical time difference between consecutive packets generation isbounded to the [0.1, 1] sec range. Length: Variable. For Example, DENMmessage may have the following characteristics. Content: Containinformation related to a variety of events. Periodicity: Event triggersthe DENM update. In between two consequent DENM updates, it is repeatedwith a pre-defined transmission interval. Length: Fixed until DENMupdate. For Example, BSM message may have the following characteristics.Content: Part I contains some of the basic vehicle state informationsuch as the message ID, vehicle ID, vehicle latitude/longitude, speedand acceleration status. Part II contains two option data frames:VehicleSafetyExtension and VehicleStatus. Periodicity: Periodic, theperiodicity may be different considering whether BSM part II is includedor not and the different application type. Length: Fixed, with differentmessage size considering whether part II exists or not.

In an example, SPS may be employed for the transmission of BSM, DENMsand CAMs. For example, the UE's speed/position/direction changes withina range. BSM may be periodic traffic with a period of 100 ms. Themessage size of BSM may be in the range of 132˜300 Bytes withoutcertificate and 241˜409 Bytes with certificate. DENMs, once triggered,may be transmitted periodically with a given message period which mayremain unchanged. The message size of the DENM may be 200˜1200 Bytes. Ifthe UE's speed/position/direction does not change or changes within asmall range, the CAM generation periodicity may be fixed.

The SPS may be supported for the UL and DL VoIP transmission. In thecurrent SPS specification, the base station may configure SPSperiodicity via dedicated RRC signaling. The periodicity of VoIP packetis generally fixed.

The UE may transmit traffic associated with multiple V2X services, whichmay require different periodicity and packet sizes. The SPS TB size andperiod may be adapted to different V2X services. Multiple parallel SPSprocesses may be activated at the UE. The SPS processes may differ inthe amount of resource blocks (RBs) allocated and/or SPS period and maycorrespond to different types of V2X packets. Once the AS layer of UEreceives the V2X packets from upper layer, the UE may trigger V2X packettransmissions on the corresponding SPS grant. Multiple UL SPSconfigurations may be configured for the UE.

The eNB may configure different SPS C-RNTIs for different SPS processesof the UE. SPS activation and release mechanism may be implemented.Employing at least one or more SPS RNTIs, the eNB may trigger which SPSprocess is activated or released. In an example implementation, in orderto support multiple SPS configurations different SPS C-RNTIs may beconfigured for different SPS traffic types. For example, a first SPSC-RNTI may be configured for SPS configuration to transmit voicetraffic, a second SPS C-RNTI may be configured for SPS configuration totransmit a V2X traffic. An eNB may transmit one or more RRC messagescomprising multiple SPS configuration parameters. The multiple SPSconfiguration parameters may comprise multiple SPS-RNTI parameters formultiple SPS traffic types (e.g. multiple UL SPS configurations).

In the current LTE standard, a maximum of one downlink SPS and/or oneuplink SPS may be configured for the PCell. Configuration of multipleSPSs are not supported for the PCell or any other cell. An SPS RNTI isconfigured for the UE to support one DL SPS configuration and/or one ULSPS configuration. The current SPS-Config IE comprises:semiPersistSchedRNTL: RNTI; sps-ConfigDL: SPS-ConfigDL; sps-ConfigUL:SPS-ConfigUL. Example embodiments enhance SPS configuration andprocesses to enable multiple SPS configuration for downlink, uplinkand/or sidelink of a cell.

In an example, CAM message generation may be dynamic in terms of size,periodicity and timing. Such changes may result in misalignment betweenSPS timing and CAM timing. There may be some regularity in size andperiodicity between different triggers. UE assistance may be needed totrigger and/or employ SPS.

FIG. 17 shows an example signaling flow for configuring and transmittingUE SPS assistance. In an example embodiment, a base station may transmitone or more RRC messages to configure reporting of UE assistanceinformation. A UE may transmit UE SPS assistance information to a basestation indicating that the UE intends to transmit data associated to anSPS configuration. In response, the base station may transmit to the UEan acknowledgement to the UE indication. A UE may provide UE assistanceinformation to a base station for V2X communications. The UE assistanceinformation may include parameters related to SPS traffic andconfigurations. Triggering of UE assistance information transmission maybe left to UE implementation. For instance, the UE may be allowed toreport the UE assistance information when change in an estimatedperiodicity and/or a timing offset of packet arrival occurs.

In an example, a base station may provide one or more SPS configurationsfor the UE via RRC signaling. SPS configurations may be for transmissionof SPS traffic via a downlink, an uplink and/or via a sidelink. When aUE needs to transmit a type of message employing SPS, the UE may reportUE SPS assistance information about one or more SPS traffic types to thebase station. UE SPS assistance information may indicate at least one ofthe following SPS assistance parameters for an SPS traffic type. The SPSassistance parameters may indicate at least one of the following:message type, logical channel, traffic/message size, SPS configurationindex, traffic type, and/or traffic periodicity. The base station maytransmit an SPS transmission grant (e.g. DCI activating an SPS) based onthe UE assistance report. The base station may provide an SPS DCI grantfor an SPS configuration and SPS radio resources based on the assistanceinformation transmitted by the UE. After receiving the grant, the UE mayinitialize the corresponding SPS configuration and may transmit the datavia the radio resources allocated to the UE. The UE assistanceinformation may enable the base station to determine logical channelsand traffic priority and size. The base station may configure/activatethe corresponding SPS for the UE. For example, legacy mechanisms do notprovide UE SPS assistance information comprising at least one logicalchannel and other assistance parameters. This improved process enhancesSPS transmission efficiency in the uplink.

In an example, multiple SPSs may be activated in parallel. For example,a new service may be triggered while a previous service is on-going. Inan example, the UE may transmit an assistance message to the basestation indicating new information about new messages (SPS traffic) fortransmission. The base station may provide a second SPS transmissiongrant for transmission of the new service/message(s). The UE may selectthe second SPS configuration and corresponding resources fortransmission of new SPS traffic. In an example, a previous SPS grant anda new SPS grant may continue in parallel.

In an example, a UE may transmit traffic associated with multiple V2Xservices, which may require different periodicity and packet sizes. TheSPS TB size and period may be adapted to different V2X services.Multiple parallel SPS processes may be activated in parallel at the UE.Different SPS processes may differ in the number of allocated resourceblocks (RBs) and/or SPS periodicity and may correspond to differenttypes of V2X packets. Once the radio layer of UE receives the V2Xpackets from a V2X application, the UE may trigger V2X packettransmissions on the corresponding SPS grant. Multiple UL SPSconfigurations may be configured for a UE.

When configuration of multiple SPSs are required, legacy mechanisms maybe extended to support multiple SPSs. The base station may configuredifferent SPS RNTIs for different SPS processes of the UE. SPSactivation and release mechanism may be implemented. The base stationmay trigger which SPS process is activated or released employing atleast one or more SPS RNTIs. In an example implementation, in order tosupport multiple SPS configurations different SPS RNTIs may beconfigured for different SPS configurations. For example, a first SPSRNTI may be configured for SPS configuration to transmit a first V2Xtraffic, a second SPS RNTI may be configured for SPS configuration totransmit a second V2X traffic. A base station may transmit one or moreRRC messages comprising multiple SPS configuration parameters. Themultiple SPS configuration parameters may comprise multiple SPS-RNTIparameters for multiple SPS configurations (e.g. multiple UL SPSconfigurations). Some of the example embodiments may implement multipleSPS RNTIs, and some may implement a single SPS RNTI.

A UE configured with multiple SPS RNTIs may need to monitor search spaceof PDCCH for multiple SPS RNTIs. When the number of required SPSconfigurations increases, this mechanism may increase UE processingrequirements and/or power consumption. Extension of legacy mechanisms,for implementation of multiple SPS configurations, increases UEprocessing requirements and battery power consumption. In an example, aUE may be configured with many SPS configurations (e.g. 4, or 8, etc)for different types of V2X traffic. There is a need to improve SPSconfiguration and activation/release mechanisms in a base station andwireless device when multiple SPSs are configured. Example embodimentsmay increase signaling overhead, however the potential benefitsoutweight the increased overhead when V2X communication is enabled.Example embodiments improve base station and UE implementations, enhancenetwork performance, reduce UE monitoring requirements, and reducebattery power consumption, when multiple SPSs are configured for a givenUE for transmission of SPS traffic via an uplink (UL) or a sidelink(SL).

In an example, multiple downlink, uplink, and/or sidelink SPSs may beconfigured for a cell. In an example, one or more SPS RNTIs may beconfigured when a plurality of SPSs are configured. In an example, anRRC message may comprise an index identifying an SPS configuration of acell. In an example, the DCI employing SPS RNTI and triggering an SPSmay include the index of the SPS that is triggered (initialized,activated) or released (deactivated). For example, the DCI activating orreleasing an uplink SPS corresponding to a V2X SPS traffic may comprisean UL SPS configuration index field (e.g. 3 bits) identifying the SPSconfiguration corresponding the SPS configuration index. SPSconfiguration index may indicate the index of one of one or more SL/ULSPS configurations. Using this enhanced mechanism multiple SPSs may beconfigured using the same SPS RNTI (e.g. for V2X traffic). This mayreduce UE battery power consumption and provide flexibility inconfiguring multiple SPSs.

In an example embodiment, when one or more SPS grant configurations areconfigured for a UE, for example, when one or more SPS-ConfigUL and/orSPS-ConfigSL are configured on a cell or when one or more SPS grantconfigurations are configured within an SPS-ConfigUL and/orSPS-ConfigSL, RRC configuration parameters may comprise an SPSconfiguration index. One or more uplink SPS configuration parameters maybe assigned to (associated with) the same SPS RNTI. Different SPSconfigurations (e.g. having different SPS periodicity) may be assignedto the same SPS RNTI, and may be identified by different SPSconfiguration indexes. In an example embodiment, one or more SPSconfigurations (e.g. multiple periodicity, MCS, and/or other parameters)may be triggered employing the same SPS RNTI, and using different SPSconfiguration indexes. FIG. 14 shows an example RRC configuration andexample DCIs activating and releasing an SPS for an uplink or asidelink. A similar mechanism may be applied to the downlink.

The example mechanism may be applied to downlink, uplink and/or sidelinkSPS configurations. For example, when one or more SPS grantconfigurations are configured for transmission of various V2X trafficvia sidelink by a UE, for example, when one or more SPS configurationsare configured for a sidelink of a cell, RRC configuration parametersmay comprise an SPS RNTI for the sidelink, and one or more SPSconfiguration indexes (each associated with a sidelink SPS RRCconfiguration). One or more uplink SPS configuration parameters may beassigned to (associated with) the same sidelink SPS RNTI for sidelinkSPS activation and release. Different SPS configurations (e.g. havingdifferent periodicity) may be assigned to the same sidelink SPS RNTI,and may be identified by different SPS configuration indexes. In anexample embodiment, one or more sidelink SPS configurations (e.g.multiple periodicity, MCS, and/or other parameters) may be triggeredemploying the same sidelink SPS RNTI for transmission of SPS V2X trafficvia a sidelink.

In an example, SPS-ConfigUL1 may be assigned SPS RNTI andSPS-ConfigIndex1, and SPS-ConfigUL2 may be assigned SPS RNTI andSPS-ConfigIndex2. A base station may transmit one or more RRC messagescomprising configuration parameters of one or more cells (e.g. PCelland/or SCell(s)). The configuration parameters may compriseconfiguration parameters for one or more SPSs. The configurationparameters may comprise the SPS RNTI, SPS-ConfigIndex1 andSPS-ConfigIndex2.

In an example, SPS-ConfigUL IE may comprise an SPS RNTI and anSPS-ConfigIndex1 and an SPS-ConfigIndex2. One or more first SPSconfiguration parameters may be associated with SPS-ConfigIndex1 and oneor more second SPS configuration parameters may be associated withSPS-ConfigIndex2. Example of SPS configuration parameters maybeperiodicity, HARQ parameter(s), MCS, grant size, and/or any other SPSconfiguration parameter presented in RRC SPS configuration. A basestation may transmit one or more RRC messages comprising configurationparameters of one or more cells (e.g. PCell and/or SCell(s)). Theconfiguration parameters may include configuration parameters for one ormore SPSs. The configuration parameters may comprise the SPS RNTI,SPS-ConfigIndex1 and SPS-ConfigIndex2.

The UE configured with SPS configurations may monitor PDCCH and searchfor a DCI associated with the SPS RNTI (e.g. scrambled with SPS-RNTI).The base station may transmit a DCI associated to SPS RNTI to the UE toactivate or release an SPS grant. The UE may decode a DCI associatedwith the SPS RNTI. The DCI may comprise one or more fields comprisinginformation about the grant. The DCI may further comprise an SPSconfiguration index. The SPS configuration index may determine which oneof the SPS configurations are activated or released.

Some of example fields in the DCI grants for an SPS in a legacy systemis employed. Many of fields are marked by N/A. In an example embodiment,one of the existing fields (e.g. one of the N/A fields), or a new fieldmay be introduced in a DCI for indicating the SPS configuration index.An SPS configuration index field in the DCI may identify which one ofthe SPS configurations is activated or released. The UE may transmit orreceive data according the grant and SPS configuration parameters.

In an example embodiment, a wireless device may receive at least onemessage comprising: a semi-persistent scheduling (SPS) cell radionetwork temporary identifier (RNTI); a first SPS configurationparameter(s); a second SPS configuration parameter(s); a first SPSconfiguration index value associated with the first SPS configurationparameters; and a second SPS configuration index value associated withthe second SPS configuration parameters. The wireless device may receivea downlink control information (DCI) associated with the SPS RNTI. TheDCI comprises one or more fields of an SPS grant and an SPSconfiguration index value. The wireless device may transmit/receive SPStraffic on radio resources identified in the SPS grant considering theSPS configuration parameters associated with the SPS configuration indexvalue. The SPS configuration parameter associated with the SPSconfiguration index may include, for example, SPS periodicity, MCS,radio resource parameters, and/or other SPS parameters included in SPSconfigurations.

In an example embodiment, an SPS grant may be for a specific messagetype. In current mechanisms, SPS configuration parameters and/or an SPSDCI grant do(es) not comprise information on traffic types associatedwith the grant. In an example embodiment, a wireless device may receiveat least one message comprising: a semi-persistent scheduling (SPS) cellradio network temporary identifier (RNTI); and a sequence of one or moreSPS configuration IEs. An SPS configuration IE may comprise SPSconfiguration parameters, SPS configuration index, and/or one or morefields indicating a traffic/resource profile (e.g. traffic index value)associated with the SPS configuration parameters. The index for thetraffic type may be a logical channel identifier, bearer identifier, V2Xtraffic type identifier, a service type, a radio resource type and/orthe like. The one or more fields may also determine a relative priorityof the traffic type compared with other traffics. The wireless devicemay receive a downlink control information (DCI) associated with the SPSRNTI. The DCI may comprise at least one of SPS Config index and/ortraffic/resource profile fields. Example embodiments may increasesignaling overhead, however the potential benefits outweight theincreased overhead when communications of various traffic types areenabled. Example embodiments enable a UE and a base station to provideSPS (periodic) resources for one or more specific traffic types. Thisprocess enhances UE uplink traffic multiplexing and enhances overallspectral efficiency of the air interface. In an example, a grant can beprovided for transmission of traffic with high priority, while lowerpriority traffic may use dynamic grants. FIG. 15 shows an example SPSconfiguration and example activation/release DCIs for transmission ofvarious traffic types. When RRC SPS configuration parameters and/or oneor more DCI fields indicate traffic/resource profile, the UE maytransmit uplink data including the corresponding traffic type in thecorresponding SPS grant.

In an example, SPS configurations may include a sequence of variousconfiguration parameters. In an example embodiment, a wireless devicemay receive at least one message comprising: a semi-persistentscheduling (SPS) cell radio network temporary identifier (RNTI); asequence of one or more SPS configuration parameters, e.g.periodicities. In an example, each of the one or more SPS configurationsparameters (e.g. SPS Config IE comprising a periodicity IE value) may beassociated with an SPS configuration index. The wireless device mayreceive a downlink control information (DCI) associated with the SPSRNTI. The DCI may comprise one or more fields of an SPS grant (e.g. afirst SPS configuration index value). The wireless device may activate(transmit/receive) SPS traffic on radio resources identified in the SPSgrant considering the SPS configuration parameters (e.g. associated withthe first SPS configuration index value). In an example, the DCI maycomprise one or more fields comprising traffic/resource profileparameters.

The DCI may comprise one or more fields indicating a traffic/resourceprofile (e.g. traffic/resource index value) associated with the SPSconfiguration parameters. The index for the traffic type may be alogical channel identifier, bearer identifier, V2X traffic typeidentifier, a service type, a radio resource type and/or the like. In anexample, the one or more fields may also determine a relative priorityof the traffic type compared with other traffics. Example embodimentsmay increase signaling overhead, however the potential benefitsoutweight the increased overhead when communications of various traffictypes are enabled. Example embodiments enable a UE and a base station toprovide SPS (periodic) resources for one or more specific traffic types.This process enhances UE uplink traffic multiplexing and enhancesoverall spectral efficiency of the air interface. In an example, a grantcan be provided for transmission of traffic with high priority, whilelower priority traffic may use dynamic grants. FIG. 16 shows an exampleactivation/release DCIs for transmission of various traffic types. Whenone or more DCI fields indicate traffic/resource profile, the UE maytransmit uplink data including the corresponding traffic type in thecorresponding SPS grant.

Example embodiments may be employed when one or more SPS RNTIs areconfigured. A given SPS traffic (message type) may be transmitted withvarious periodicity depending on vehicle speed or other parameters.Example embodiments enable updating SPS grant configuration without theneed for reconfiguring SPS grants. Example embodiments may be employedfor activation or release of an SPS configuration.

In an example, multiple SPSs may be activated in parallel. For example,a new SPS may be triggered while a previous SPS is on-going. In anexample, the UE may transmit to a base station a message comprisingassistant information indicating that the UE requires new SPS resourcesfor transmission of new messages. The assistant information may compriseinformation about at least one SPS traffic type, e.g. logical channel,periodicity, message size, and/or the like. The base station may providean SPS grant for the new service/message(s). The UE may employ an SPSconfiguration and a corresponding SPS resources for uplink transmissionof a corresponding traffic. In an example, a previous SPS grant and anew SPS grant may be employed in parallel. FIG. 13 shows an example whenmultiple SPS grants are activated in parallel. A base station maytransmit SPS grant 1 in a first subframe for transmission of a first SPStraffic. The base station may transmit SPS grant 2 in a second subframefor transmission of a second SPS traffic. The first SPS grant and thesecond SPS grant may have different parameters, for example, maycomprise different RBs assignments, may have different periodicity, mayhave different DCI and RRC configuration parameter(s), and/or the like.In an example embodiment, an instance of the first SPS grant and aninstance of the second SPS grant may overlap in the same subframe.

In an example embodiment, a base station scheduling mechanism may avoidor reduce the possibility of such a scenario. Such limitation may addadditional complexity and constraint on base station schedulingmechanism and may reduce overall spectral efficiency in the uplink.There is a need to implement mechanisms for a UE and/or base station toenhance uplink transmission mechanisms when multiple uplink SPS grantscoincide in the same subframe and/or TTI.

In an example embodiment, multiple uplink SPSs are configured on a cell,for example, with different periodicity, or other parameters. In anexample, some of the RRC parameters may be the same for various SPSconfigurations on a cell. For example, when multiple SPSs are configuredon a cell, the SPSs may employ the same p0-Persistent, and/orp0-PersistentSubframeSet2-r12 to enable the same uplink powercalculation configuration for multiple SPSs on the cell. In an example,some other parameters, such as twolntervalsConfig, implicitReleaseAfter,and/or MCS (if configured as an RRC parameter) may be the same acrossmore than one SPS configuration. Multiple SPS configurations may havethe same common parameters, and have its own SPS specific parameter.

In an example, DCI format 0 may be used for the scheduling of PUSCH inone UL cell. Other DCI formats may be used for downlink or uplink SPSgrants. When multiple SPS are activated in parallel, some instances ofthe SPSs may coincide in the same subframe. The UE may be able totransmit on both grants in the same subframe when some of thetransmission parameters are the same across SPS grants. For example, theUE may transmit on multiple grants in the same subframe, when the grantshave the same MCS, and/or same hopping pattern. In an example,additional limitations may apply. For example, two grants may need tohave the same Cyclic shift for DM RS and OCC index, and/or may need tohave adjacent RB assignments. In an example embodiment, a base stationscheduling mechanism may consider these constraints when activatingparallel SPSs on a cell (for example, when an instance of SPS grantscoincides on the same subframe). In an example, parallel transmissionbased on multiple grants on a subframe may be implemented.

In an example, a UE may aggregate multiple grants in a subframe. Forexample, the UL PUSCH transmit power may be calculated considering thecommon RRC configuration parameters, aggregated RBs for both grants, andpower control parameters for the cell on the subframe containing bothgrants. The UE may add the number of RBs in the first grant and thesecond grant to calculate the number of RBs for uplink transmission. TheUE may consider the same MCS for both grants in calculating the power.If the two grants have the same MCS, the MCS may be either MCS of thegrants. If the two grants have different MCSs, the UE may consider themore stringent MCS (lower modulation and coding), MCS of the higherpriority grant, or one of the two MCS according to a UE implementationrule. The UE may transmit both grants employing the same MCS that isemployed for power control calculations. In an example, a MAC TB may betransmitted on the resources assigned in the aggregate of multiplegrants. The base station may transmit an ACK for the received TB. In anexample, MAC TBs of each grant may be built and transmitted on theassociated grant. When multiple TBs are transmitted, the base stationmay transmit different ACK/NACK for different grants.

In an example, when multiple SPS grants coincide in the same subframe,the UE may calculate the power of each grant separately based on PUSCHpower calculation formula. Example PUSCH power calculation method isshown in below. Other example formula and scenarios are described in theAppendix.

${P_{{PUSCH},c}(i)} = {\min {\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{{10\; {\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\; \_ \; {PUSCH}},c}(j)} +} \\{{{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}$

In the event that the sum of the powers of multiple SPS grants in thesubframe exceeds PcMAX, the UE may scale the transmit powers so that thesum of the powers is below the PcMAX. In an example, the UE may assign ahigher priority to power of one of the grants compared with the otherone(s). In an example, the UE may use a predetermined rule to determinethe priority, e.g., based on the grant priority, size of the grant, MCS,and/or timing of the grant.

In an example, the UE may calculate the PUSCH power of PUSCH for eachgrant without considering PcMAX. The UE may add the power of PUSCHs, andwhen the total power exceeds PcMAX, the UE may employ a scaling rule toscale the transmit powers, so that transmit power on a cell does notexceed PcMAX.

${P_{{PUSCH},c}(i)} = {\min \begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{{P_{{PUSCH},c}(i)}_{{grant}\; 1} + {P_{{PUSCH},c}(i)}_{{grant}\; 2}}\end{Bmatrix}}$

In an example, when multiple SPS grants coincide in the same subframe,the UE may employ some of the grant parameters (e.g. MCS, and/or powerparameters) of a selected grant (e.g. a grant with a higher priority).In an example, the UE may select one of the grants based on criteria,e.g. the grants that was received first, higher priority grant, largergrant, grant associated with a logical channel with higher priorityand/or according to a predefined implementation rule. The UE may usesome the parameters of the selected grant for uplink transmission formultiple grants. The UE may calculate the power based on the parametersof the selected grant, e.g. employing the above example methods.

In an example, when multiple SPS grants coincide in the same subframe,the UE may transmit uplink TBs employing a selected grant (e.g. a grantwith a higher priority). The UE may drop other grant(s). In an example,the UE may select one of the grants based on criteria, e.g. the grantsthat was received first, the higher priority grant, the larger grant,grant associated with a logical channel with higher priority and/oraccording to a predefined implementation rule. The UE may transmituplink signals employing the selected grant. The UE may drop/ignoreother grant(s) and may not transmit uplink signals (TBs) in the othergrant(s). The base station may be configured with this rule, and may notexpect to receive TBs in a grant that is dropped/ignored.

In an example, when multiple SPS grants coincide in the same subframe n,the UE may transmit uplink TB s employing a selected grant (e.g. a grantwith a higher priority) in the subframe n. The UE may shift othergrant(s) and employ those grants for subframe n+k, e.g. k=1 (othervalues fork may also implemented, e.g. k==1, 2, etc). In an example, theUE may select one of the grants based on criteria, e.g. the grants thatwas received first, the higher priority grant, the larger grant, and/oraccording to a predefined implementation rule. The UE may transmituplink signals in subframe n employing the selected grant. The UE mayemploy the other grant(s) for subframe n+k, and may transmit uplinksignals (TBs) for the other grant(s) in subframe n+k. For example, k=1for a second grant, and k=2 for a third grant. This mechanism may bepreconfigured in the UE and base station, the base station may expect toreceive TB(s) for the other grant in subframe n+k, and may not schedulethose resources for other UEs.

Example embodiments may be preconfigured in the UE and base station, thebase station may expect to receive TB(s) according to the examplemechanism. Some of the examples may be combined, and different UEs mayimplement different example implementations based on UE configurationand/or capability.

According to various embodiments, a device (such as, for example, awireless device, off-network wireless device, a base station, and/or thelike), may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 25 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2510, a first base station may receive, froma wireless device, at least one first message 1800. The first message1800 may comprise UE SPS/V2X capabilities comprising a parameterindicating whether the wireless device supports multiple uplink semipersistent scheduling (SPS) configurations for V2X communications.According to an embodiment, the at least one parameter may furtherindicate whether the wireless device supports reporting SPS assistanceinformation. According to an embodiment, the at least one parameter mayfurther indicate whether the wireless device supports V2X communicationswith the base station.

At least one second (RRC) message, e.g. 1810 and/or 1830, may beselectively transmitted at 2520 when the parameter indicates support ofthe multiple SPS configurations. The at least one second message maycomprise: an uplink SPS radio network temporary identifier (RNTI), atleast one uplink SPS configuration parameter, and an SPS configurationindex for the at least one uplink SPS configuration parameter. Adownlink control information (DCI) corresponding to the uplink SPS RNTImay be transmitted at 2530. The DCI may comprise the SPS configurationindex. At 2540, at least one transport block may be received employingthe at least one uplink SPS configuration parameter. FIG. 13 throughFIG. 17 show multiple examples of RRC configurations and DCIs. Accordingto an embodiment, the DCI may indicate activation of the at least oneuplink SPS configuration. The DCI may further comprise at least oneresource parameter. The first base station may receive the at least onetransport block in a subframe employing the at least one resourceparameter. The subframe may be determined employing an uplink SPSinterval of the at least one uplink SPS configuration parameter.According to an embodiment, the at least one uplink SPS configurationparameter may comprise at least one parameter indicating one or moretraffic types corresponding to the uplink SPS IE. According to anembodiment, the at least one uplink SPS configuration parameter maycomprise at least one parameter indicating one or more traffic typescorresponding to the uplink SPS IE. According to an embodiment, the DCImay comprise at least one parameter indicating one or more traffic typescorresponding to the uplink SPS IE.

According to an embodiment, the first base station may further transmit,to a second base station and in response to the first base stationmaking a handover decision for the wireless device, a second message1840 comprising the UE SPS/V2X capabilities comprising the parameterindicating whether the wireless device supports multiple uplink SPSconfigurations for V2X communications.

FIG. 26 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2610, a wireless device may transmit, to afirst base station, at least one first message 1800. The at least onefirst message may comprise UE SPS/V2X capabilities comprising aparameter indicating that the wireless device supports multiple uplinksemi persistent scheduling (SPS) configurations for V2X communications.At least one second (RRC) message, e.g. 1810 and/or 1830, may bereceived at 2620. The at least one second message may comprise: anuplink SPS radio network temporary identifier (RNTI), at least oneuplink SPS configuration parameter, and an SPS configuration index forthe at least one uplink SPS configuration parameter. At 2630, a downlinkcontrol information (DCI) may be received. The DCI may correspond to theuplink SPS RNTI. The DCI may comprise the SPS configuration index. At2640, at least one transport block may be transmitted employing the atleast one uplink SPS configuration parameter.

FIG. 27 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2710, a determination may be made whether afirst base station makes a handover decision for a wireless device. Inresponse to a positive determination, the first base station maytransmit to a second base station at 2720, a first message 1840comprising UE SPS/V2X capabilities comprising a parameter indicatingwhether the wireless device supports multiple uplink semi persistentscheduling (SPS) configurations for V2X communications. According to anembodiment, the first message 1840 may indicate the configurationparameters of the at least one SPS when the wireless device supports themultiple SPS configurations. At 2730, a second message 1850 may bereceived from the second base station. The second message may comprisean information element indicating configuration parameters of at leastone SPS. The configuration parameters may comprise: an uplink SPS radionetwork temporary identifier (RNTI), at least one uplink SPSconfiguration parameter, and an SPS configuration index for the at leastone uplink SPS configuration parameter. At 2740, a third message 1860may be transmitted to the wireless device. The third message 1860 maycomprise the information element indicating the configuration parametersof the at least one SPS configuration.

According to an embodiment, the first message 1840 further comprisesfirst configuration parameters for a first plurality of SPSs. Accordingto an embodiment, the first base station may receive from the wirelessdevice and prior to transmitting the first message 1840, at least onefourth message 1800 comprising UE SPS/V2X capabilities comprising theparameter indicating whether the wireless device supports the multipleuplink SPS configurations.

FIG. 28 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2810, a base station may receive, from awireless device, a message 1800 comprising UE SPS/V2X capabilitiescomprising a first sequence of a plurality of parameters. The UE SPS/V2Xcapabilities may also comprise the parameter indicating whether thewireless device supports the multiple uplink SPS configurations.

FIG. 19 shows an example of UE V2X capabilities comprising the firstsequence and the second sequence. A first parameter in the firstsequence may indicate whether a V2X transmission configuration issupported in a first band combination. The first band combination may bein a second sequence of a plurality of band combinations associated withthe wireless device. An index of the first parameter in the firstsequence may identify the first band combination in the second sequence.According to an embodiment, the first band combination may comprise athird sequence of one or more band identifiers, and a band identifier ofthe sequence may indicate a specific band. At 2820, a second (RRC)message, e.g. 1810 and/or 1830, may be transmitted based on the message1800. The second message, e.g. 1810 and/or 1830, may compriseconfiguration parameters of at least one cell for V2X communications.The at least one cell may operate in one of the plurality of bandcombinations that supports the V2X transmission configuration.

FIG. 19 shows an example of UE V2X capabilities comprising the firstsequence and the second sequence. In an example embodiment, the basestation may receive a message comprising UE SPS/V2X capabilities may bereceived e.g. via a first signaling bearer on the primary cell. Theplurality of UE SPS/V2X capability parameters may comprise a firstsequence of one or more parameters. A first parameter in the firstsequence may indicate whether a V2X transmission configuration issupported for first band combination. The first band combination may bein a second sequence of one or more band combinations. The index of thefirst parameter in the first sequence may determine the index of thefirst band combination in the second sequence. According to some of thevarious embodiments, the size of the first sequence may be the same asthe size of the second sequence. The index may determine the order of:the first parameter in the first sequence; and the first bandcombination in the second sequence. The first band combination may beidentified by a first band combination parameter. The first bandcombination parameter may comprise a list of band identifier(s). Each ofthe band identifier(s) may be one of a finite set of numbers. Each ofthe numbers may identify a specific band. According to some of thevarious embodiments, the wireless device may support one or moreinter-band V2Xs if the list of band identifier(s) includes more than oneband; and the first parameter indicates that V2X is supported. In anexample embodiment, the wireless device may support multiple intra-bandV2X if the list of band identifier(s) includes one band; and the firstparameter indicates that SPS/V2X is supported.

According to an embodiment, the second message, e.g. 1810 and/or 1830,may comprise: an uplink SPS radio network temporary identifier (RNTI),at least one uplink SPS configuration parameter, and an SPSconfiguration index for the at least one uplink SPS configurationparameter. According to an embodiment, the base station may furthertransmit a downlink control information (DCI) corresponding to theuplink SPS RNTI 1830. The DCI may comprise the SPS configuration index.According to an embodiment, the base station may further receive atleast one transport block employing the at least one uplink SPSconfiguration parameter. According to an embodiment, the DCI mayindicate activation of the at least one uplink SPS configuration. TheDCI may further comprise at least one resource parameter. The basestation may further receive the at least one transport block in asubframe employing the at least one resource parameter. The subframe maybe determined employing an uplink SPS interval of the at least oneuplink SPS configuration parameter. According to an embodiment, the atleast one uplink SPS configuration parameter may comprise at least oneparameter indicating one or more traffic types corresponding to theuplink SPS IE. According to an embodiment, the at least one uplink SPSconfiguration parameter may comprise at least one parameter indicatingone or more traffic types corresponding to the uplink SPS IE. Accordingto an embodiment, the DCI may comprise at least one parameter indicatingone or more traffic types corresponding to the uplink SPS IE.

According to an embodiment, the first base station may transmit, to asecond base station and in response to the first base station making ahandover decision for the wireless device, a first message 1850comprising UE SPS/V2X capabilities comprising the first sequence of theplurality of parameters. According to an embodiment, the first messagemay further comprise first configuration parameters for a firstplurality of SPSs. The first base station may receive from the secondbase station, a second message 1850 comprising an information elementindicating configuration parameters of at least one SPS. Theconfiguration parameters may comprise, an uplink SPS radio networktemporary identifier (RNTI), an SPS configuration index indicating anindex of at least one uplink SPS configuration parameter, and at leastone uplink SPS configuration parameter. A third message 1860 may betransmitted to the wireless device. The third message may comprise theinformation element indicating the configuration parameters of the atleast one SPS configuration.

FIG. 29 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2910, a base station may receive, from awireless device, a message comprising a plurality of capabilityparameters comprising UE SPS/V2X capabilities. FIG. 20 shows an exampleUE V2X capability parameters. The plurality of UE V2X capabilityparameters may indicate a supported list of band combinations on whichthe wireless device supports a first configuration of V2Xcommunications. A band combination of the supported list of bandcombinations may comprise a sequence of one or more band identifiers. Aband identifier of the sequence may indicate a specific band. Accordingto an embodiment, the plurality of capability parameters may furtherindicate configuration parameters for each of the supported list of bandcombinations. In an example, configuration parameters for a supportedband combination may indicate a transmit power class for the bandcombination, and/or an uplink and/or sidelink configuration for the bandcombination. In an example, configuration parameters for a supportedband combination may indicate configuration parameter(s) for a band inthe band combination. For example, configuration parameters for asupported band combination may indicate a transmit power class, oruplink/sidelink configuration, modulation configuration, configurationof link parameters/timers for each band in the band combination.

FIG. 20 shows an example UE V2X capability parameters. The plurality ofUE SPS/V2X capability parameters may indicate a supported list of bandcombinations on which the wireless device supports a first configurationof V2X communications. In an example implementation, the plurality of UESPS/V2X capability parameters may comprise a first sequence of one ormore parameters. A first parameter in the first sequence may indicatewhether a V2X transmission configuration is supported for first bandcombination. The first band combination may be in a second sequence ofone or more band combinations. The index of the first parameter in thefirst sequence may determine the index of the first band combination inthe second sequence. In an example, a list (sequence) of one or moresupported band combination may be supported. Each IE in the list maycomprise band identifiers of a band combination. The plurality ofcapability parameters may further indicate radio configurationparameters for each of the supported list of band combinations. In anexample, configuration parameters for a supported band combination mayindicate a transmit power class for the band combination, and/or anuplink and/or sidelink configuration for the band combination. In anexample, configuration parameters for a supported band combination mayindicate configuration parameter(s) for a band in the band combination.For example, configuration parameters for a supported band combinationmay indicate a transmit power class, or uplink/sidelink configuration,modulation configuration, configuration of link parameters/timers foreach band in the band combination.

At 2920, a second (RRC) message, e.g. 1810 and/or 1830, may betransmitted based on parameters comprised in the message 1800. Thesecond message may comprise configuration parameters of at least onecell operating in one of the band combinations that supports the V2Xcommunications. According to an embodiment, the second message maycomprise: an uplink SPS radio network temporary identifier (RNTI), atleast one uplink SPS configuration parameter, and an SPS configurationindex for the at least one uplink SPS configuration parameter. Accordingto an embodiment, the base station may further transmit a downlinkcontrol information (DCI) corresponding to the uplink SPS RNTI. The DCImay comprise the SPS configuration index. At least one transport blockmay be further received employing the at least one uplink SPSconfiguration parameter.

FIG. 30 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3010, a base station may receive, from awireless device, a first message 1800 comprising UE SPS/V2X capabilitiescomprising a band combination configuration. FIG. 21 shows an example ofthe band combination configuration. The band combination configurationmay comprise a first sequence of a plurality of band parameters. A firstband parameter in the first sequence may comprise: a first bandidentifier indicating a first band, a first radio configurationparameter, and at least one parameter indicating whether at least oneV2X configuration is supported in the first band. Example, V2Xconfiguration may be sidelink V2X communication, uplink V2Xcommunication, a power class, a V2X transmission capability, and/or thelike. At 3020, a second (RRC) message, e.g. 1810 and/or 1830, may betransmitted employing the parameters in the first message 1800. Thesecond message may comprise configuration parameters of at least onecell operating in at least one band indicated in the first sequence.

FIG. 21 shows an example of the band combination configuration. Theplurality of radio capability parameters may comprise a first sequenceof one or more radio configuration IEs. A radio configuration IE in thesequence comprises radio configuration parameters for V2X/SPS and afirst parameter indicating whether SPS/V2X may be supported for a firstband. A band may be identified by a band identifier. A band combinationmay comprise a list of band identifier(s). Each of the bandidentifier(s) may be one of a finite set of numbers. Each of the numbersmay identify a specific band.

According to an embodiment, a first base station may transmit to asecond base station and in response to the first base station making ahandover decision for the wireless device, a first message 1840comprising UE SPS/V2X capabilities comprising the first sequence of theplurality of parameters. According to an embodiment, the first messagemay further comprise first configuration parameters for a firstplurality of SPSs. According to an embodiment, a second message 1850 maybe received from the second base station. The second message 1850 maycomprise an information element indicating configuration parameters ofat least one SPS. The configuration parameters may comprise: an uplinkSPS radio network temporary identifier (RNTI), an SPS configurationindex indicating an index of at least one uplink SPS configurationparameter, and the at least one uplink SPS configuration parameter.

According to an embodiment, the second message 1850 may comprise: anuplink SPS radio network temporary identifier (RNTI), at least oneuplink SPS configuration parameter, and an SPS configuration index forthe at least one uplink SPS configuration parameter. According to anembodiment, downlink control information (DCI) corresponding to theuplink SPS RNTI may be transmitted. The DCI may comprise the SPSconfiguration index. According to an embodiment, at least one transportblock may be received employing the at least one uplink SPSconfiguration parameter. According to an embodiment, the DCI mayindicate activation of the at least one uplink SPS configuration.According to an embodiment, the DCI may further comprise at least oneresource parameter. According to an embodiment, receiving the at leastone transport block in a subframe may further employs the at least oneresource parameter. According to an embodiment, the subframe may bedetermined employing an uplink SPS interval of the at least one uplinkSPS configuration parameter.

According to an embodiment, a third message 1860 may be transmitted tothe wireless device. The third message may comprise the informationelement indicating the configuration parameters of the at least one SPSconfiguration.

The base station may configure multiple SPS configurations for a givenUE. In an example, SPS-configuration-specific MCS and/orSPS-configuration-specific periodicity may be configured. Some SPSparameters may differ across the SPS-configurations. The base stationmay dynamically trigger/release the different SPS-configurations by useof (E)PDCCH. The UE may transmit to the base station SPS assistanceinformation indicating that the UE intends to transmit data before atransmission associated to an SPS configuration.

SPS/V2X configuration in the specification refers to V2X and/or enhancedSPS configuration supporting multiple uplink and/or sidelink SPSconfiguration and reporting SPS assistance information. SPS/V2Xconfiguration may support enhanced SPS configuration features, includingat least one of: configuration of multiple SPSs for a UE, reporting SPSassistance information, supporting V2X communications via uplink (e.g.UU air interface), SPS configuration and capability on SCells for a UE,and/or other enhanced SPS features. These configurations may not benecessarily employed for V2X and may be applicable to otherapplications. In an example, SPS/V2X feature may be referred to SPS orenhanced SPS feature. In an example, SPS/V2X feature may indicateconfiguration of V2X services on a specific band or a band combination.A UE may support V2X communications on a specific band or a specificband combination depending on UE transmitter/receiver capabilities. Inan example, for a given LTE-A configured cell communications (e.g. usinga first band combination), a wireless device may or may not support V2Xcommunications. A UE may support different V2X transmissionconfiguration parameters in different frequency bands depending on UEtransmitter/receiver capability.

A UE may be configured with a first SPS/V2X configuration with a servingbase station. A target base station may maintain the same SPS/V2Xconfiguration, or may update the UE SPS/V2X configuration. The targetbase station may have a different cell configuration and may require adifferent SPS/V2X configuration. In an example embodiment, the targetbase station may employ cells with the same frequencies as the servingcell and may require maintaining the same SPS/V2X configuration. Thetarget base station may configure SPS/V2X configuration after thehandover is completed or may configure SPS/V2X configuration during thehandover process. Release 13 of LTE does not support SPS/V2Xconfiguration, and addressing the SPS/V2X configuration changes duringhandover is not addressed in release 13 LTE technology. There is a needfor developing signaling flows, UE processes, and base station processesto address SPS/V2X configuration, and SPS/V2X configuration parameterhandling during the handover to reduce the handover overhead and delay,and increase handover efficiency. There is a need to develop handoversignaling and handover message parameters to address SPS/V2Xconfiguration during a handover process.

According to some of the various aspects of embodiments, inRRC_connected mode, the network may control UE mobility, for example,the network may decide when the UE connects to which E-UTRA cell(s) orinter-RAT cell. For network controlled mobility in RRC_connected, thePCell may be changed using an RRC Connection Reconfiguration messageincluding the mobilityControlInfo (handover). The SCell(s) may bechanged using the RRC connection reconfiguration message either with orwithout the mobilityControlInfo. The network may trigger the handoverprocedure e.g. based on radio conditions, load, QoS, UE category, and/orthe like. To facilitate this, the network may configure the UE toperform measurement reporting (possibly including the configuration ofmeasurement gaps). The network may also initiate handover blindly, forexample without having received measurement reports from the UE. Beforesending the handover message to the UE, the source base station mayprepare one or more target cells. The source base station may select thetarget PCell. The source base station may also provide the target basestation with a list of best cells on each frequency for whichmeasurement information is available, for example, in order ofdecreasing RSRP. The source base station may also include availablemeasurement information for the cells provided in the list. The targetbase station may decide which SCells are configured for use afterhandover, which may include cells other than the ones indicated by thesource base station.

FIG. 18 shows an example signaling flow for UE configuration andhandover process. The UE may transmit and/or receive other messages (notshown in the figure) in addition to the messages FIG. 18. For example, aUE may transmit one or more messages comprising measurement reports tothe serving base station to assist the serving base station in making ahandover decision. In an example, there may be additional communicationsof RRC messages between the UE and base station(s). In an example, someof the messages may be combined, for example, RRC message 1810 mayconfigure SPS configurations indicated in message 1830.

In an example, a UE may transmit to a base station a message 1800comprising SPS/V2X capabilities of the UE. A base station transmit oneor more RRC messages (e.g. 1810, and/or 1830) providing one or more SPSconfigurations for the UE. SPS configurations may be for transmission ofSPS traffic via a downlink, an uplink and/or via a sidelink. When a UEneeds to transmit a type of message employing SPS, the UE may transmit amessage/report 1820 comprising a UE SPS assistance information about oneor more SPS traffic types to the base station. UE SPS assistanceinformation may indicate at least one of the following SPS assistanceparameters for an SPS traffic type. The SPS assistance parameters mayindicate at least one of the following: message type, logical channel,traffic/message size, SPS configuration index, traffic type, and/ortraffic periodicity. The base station may transmit an SPS transmissiongrant (e.g. DCI activating an SPS) based on the UE assistance report.The base station may transmit SPS RRC configurations and/or an SPS DCIgrant 1830 for an SPS configuration and SPS radio resources based on theassistance information transmitted by the UE. After receiving the grant,the UE may initialize the corresponding SPS configuration and maytransmit the data via the radio resources allocated to the UE. The UEassistance information may enable the base station to determine logicalchannels and traffic priority and size. The base station mayconfigure/activate the corresponding SPS for the UE. For example, legacymechanisms do not provide UE SPS assistance information comprising atleast one logical channel and other assistance parameters. This improvedprocess enhances SPS transmission efficiency in the uplink.

In an example, the source base station may initiate the handoverprocedure by sending a handover request message 1840 to one or morepotential target base stations. The target base station may generate amessage 1850 used to configure the UE for the handover. For example, themessage 1850 may include the access stratum configuration to be used inthe target cell(s). The source base station may transmit a message 1860to the UE. The message 1860 may transparently (for example, does notalter values/content) forward the handover information received from thetarget base station to the UE. When appropriate, the source base stationmay initiate data forwarding for (a subset of) the dedicated radiobearers. After receiving the handover message, the UE may attempt toaccess the target PCell at the available RACH occasion according to arandom access resource selection at process 1870. When allocating adedicated preamble for the random access in the target PCell, the targetbase station may make the preamble available from the first RACHoccasion the UE may use. Upon successful completion of the handover, theUE may send a message (as a part of process 1870) used to confirm thehandover to the target base station.

In an example, if the target base station does not support the releaseof RRC protocol which the source base station used to configure the UE,the target base station may be unable to comprehend the UE configurationprovided by the source base station. In this case, the target basestation may use the full configuration option to reconfigure the UE forhandover and re-establishment. Full configuration option includes aninitialization of the radio configuration, which makes the procedureindependent of the configuration used in the source cell(s) with theexception that the security algorithms are continued for the RRCre-establishment.

In an example, after the successful completion of handover, PDCP SDUsmay be re-transmitted via the target cell(s). This may apply fordedicated radio bearers using RLC-AM mode and/or for handovers notinvolving full configuration option. After the successful completion ofhandover not involving full configuration option, the SN (sequencenumber) and/or the HFN (hyper frame number) may be reset for some radiobearers. For the dedicated radio bearers using RLC-AM mode both SN andHFN may continue. For reconfigurations involving the full configurationoption, the PDCP entities may be newly established (SN and HFN may notcontinue) for dedicated radio bearers irrespective of the RLC mode. UEbehavior to be performed upon handover may be the same regardless of thehandover procedures used within the network (e.g. whether the handoverincludes X2 or S1 signaling procedures).

The source base station may, for some time, maintain a context to enablethe UE to return in case of handover failure. After having detectedhandover failure, the UE may attempt to resume the RRC connection eitherin the source PCell or in another cell using the RRC re-establishmentprocedure. This connection resumption may succeed if the accessed cellis prepared. For example, when the access cell is a cell of the sourcebase station or of another base station towards which handoverpreparation has been performed. The cell in which the re-establishmentprocedure succeeds becomes the PCell while SCells, if configured, may bereleased.

Normal measurement and mobility procedures may be used to supporthandover to cells broadcasting a CSG (closed subscriber group) identity.In addition, E-UTRAN may configure the UE to report that it is enteringor leaving the proximity of cell(s) included in its CSG whitelist.E-UTRAN may request the UE to provide additional information broadcastby the handover candidate cell e.g. cell global identity, CSG identity,CSG membership status. E-UTRAN may use the proximity report to configuremeasurements as well as to decide whether or not to request additionalinformation broadcast by the handover candidate cell. The additionalinformation may be used to verify whether or not the UE is authorised toaccess the target PCell and may also be needed to identify handovercandidate cell. This may involve resolving PCI confusion, for example,when the physical layer identity that is included in the measurementreport may not uniquely identify the cell.

According to some of the various aspects of embodiments, configurationof SPS/V2X may be configured by the serving base station with RRCsignaling e.g. employing message(s) 1810 and/or 1830. The mechanism forSPS/V2X configuration and reconfiguration may be based on RRC signaling.When needed, configuration of SPS/V2X may be reconfigured with RRCsignaling. In an example, the mapping between an SCell and a SPS/V2Xconfiguration may not be reconfigured with RRC while the SCell isconfigured. For example if there is a need modify SPS/V2Xconfigurations, at least one RRC message, for example at least one RRCreconfiguration message, may be send to the UE to reconfigure SPS/V2Xconfigurations.

According to some of the various aspects of embodiments, a base stationmay consider UE's capability in configuring one or more SPS/V2X for aUE. A UE may be configured by a base station with a configuration thatis compatible with UE capability. SPS/V2X capability may be an optionalfeature in LTE release 14 (and/or beyond). UE may transmit its SPS/V2Xcapability to base station via an RRC message 1800 and base station mayconsider UE capability in configuring SPS/V2X configuration e.g.employing message(s) 1810 and/or 1830.

The purpose of RRC connection reconfiguration procedure may be to modifyan RRC connection, e.g. to establish, modify and/or release RBs, toperform handover, to setup, modify, and/or release measurements, to add,modify, and/or release SCells. As part of the procedure, NAS dedicatedinformation may be transferred from E-UTRAN to the UE. If the receivedRRC connection reconfiguration message includes the sCellToReleaseList,UE performs SCell release. If the received RRC connectionreconfiguration message includes the sCellToAddModList, UE performsSCell additions or modification.

The UE context within the source base station may contain informationregarding roaming/handover restrictions which may be provided either atconnection establishment or at the last TA (tracking area) updateprocess. The source base station may configure the UE measurementprocedures employing at least one RRC connection reconfigurationmessage. The UE may be triggered to send at least one measurement reportby the rules set by, for example, system information, RRC configuration,and/or the like. The source base station may make a handover decisionbased on many parameters, for example, the measurement reports, RRMinformation, traffic and load, a combination of the above, and/or thelike. The source base station may initiate the handover procedure bysending a handover request message 1840 to one or more potential targetbase stations. When the source base station sends the handover requestmessage 1840, it may start a handover preparation timer. Upon receptionof the handover request acknowledgement message 1850 the source basestation may stop the handover preparation timer.

The source base station may transmit a handover request message 1840 toone or more potential target base station passing information to preparethe handover at the target side. The handover request message 1840 maycomprise SPS/V2X capability information of the UE. The target basestation may employ the SPS/V2X capability of the UE in order to properlyconfigure SPS/V2X configuration of the UE before UE connects to thetarget UE. The target base station may configure the UE considering theSPS/V2X configuration limitations and capabilities of the UE. Forexample, if the UE does not support a specific SPS/V2X capability, thetarget base station may not configure the UE with a SPS/V2X(s) requiringthe specific SPS/V2X capability. In an example, if the UE does notsupport SPS/V2X configurations in certain band(s) or with a certain bandcombination, the base station may consider this limitation forconfiguring SPS/V2X for the UE. In an example, a UE may not supportSPS/V2X configuration, and base station may consider this in configuringthe UE before the UE accesses the target base station. In an example,handover request message 1840 may further comprise a current SPS/V2Xconfiguration of the UE connected to the serving base station.

During the handover preparation phase, the serving base station maytransmit one or more handover requests 1840 comprising UE's SPS/V2Xcapabilities and/or UE's current SPS/V2X configuration (SPS/V2X of theUE in connection with the serving base station) to one or more potentialtarget base stations. This information may be employed, at least inpart, by the potential target base station(s) to configure the UE, forexample, to configure SPS/V2X configuration parameters.

Handover admission control may be performed by the target base stationdependent on many factors, for example, QoS required for the UE bearers,UE capabilities, UE configuration, target base station load, acombination of the above, and/or the like. The target base station mayconfigure the required resources according to the received informationfrom the serving base station and may reserve a C-RNTI and/or a RACHpreamble. The access stratum configuration to be used in the target cellmay be specified independently (for example as an establishment) or as adelta compared to the access stratum-configuration used in the sourcecell (for example as a reconfiguration).

The target base station may prepare handover with L1/L2 and may send thehandover request acknowledge message 1850 to the source base station.The handover request acknowledge message 1850 may include a transparentcontainer to be sent to the UE as an RRC message to perform thehandover. The container may include a new C-RNTI, target base stationsecurity algorithm identifiers for the selected security algorithms, adedicated RACH preamble, access parameters, SIB s, and/or otherconfiguration parameters. The transparent container may further comprisethe SPS/V2X configurations for connection of the UE to the target basestation. The SPS/V2X configurations may modify the SPS/V2X of the UE ormay keep the same SPS/V2X configuration that the UE has with the servingbase station. The target base station may generate the RRC message toperform the handover, for example, RRC connection reconfigurationmessage including the mobility control information. The RRC message maybe sent by the source base station towards the UE in RRC handovercommand 1860. The source base station may perform the necessaryintegrity protection and ciphering of the message 1860. The UE mayreceive the RRC connection reconfiguration message 1860 from the sourcebase station and may start performing the handover at 1870. The UE maynot need to delay the handover execution for delivering the HARQ/ARQresponses to the source base station.

After receiving the RRC connection reconfiguration message including themobility control information 1860, UE may perform synchronisation to thetarget base station and accesses the target cell via RACH on the primarycell at process 1870. A UE Random access procedure may employ acontention-free procedure if a dedicated RACH preamble was indicated inthe mobility control information. The UE random access procedure mayemploy a contention-based procedure if no dedicated preamble wasindicated. The UE may derive target base station specific keys and mayconfigure the selected security algorithms to be used in the targetcell. The target base station may respond with uplink allocation andtiming advance. After the UE has successfully accessed the target cell,the UE may send an RRC connection reconfiguration complete message(C-RNTI) to confirm the handover and to indicate that the handoverprocedure is completed for the UE. The UE may transmit a MAC uplinkBuffer Status Report (BSR) Control Element (CE) along with the uplinkRRC Connection Reconfiguration Complete message or may transmit a MACuplink BSR CE whenever possible to the target base station at process1870. The target base station verifies the C-RNTI sent in the RRCConnection Reconfiguration Complete message. The target base station maynow begin sending data to the UE and receiving data from the UE.

According to some of the various aspects of embodiments, a serving basestation may receive a first message 1800 from a wireless device (e.g. ona primary cell in a plurality of cells). The first message 1800 may bean RRC UE capability message. The plurality of cells may comprise theprimary cell and at least one secondary cell. The base station mayreceive a plurality of radio capability parameters from the wirelessdevice. The first message 1800 may comprise at least one parameterindicating whether the wireless device supports configuration ofSPS/V2X(s).

In an example embodiment, the capability message 1800 may comprise oneor more parameters explicitly and/or implicitly indicating that the UEsupport configuration of SPS/V2X. For example, a parameter may indicatethat the UE is capable of handling some types of V2X configuration, andthis may imply that the UE is SPS/V2X capable. In an example, aparameter may indicate that the UE is capable of supporting a set ofenhanced configuration parameters including enhanced SPS (e.g. SPS/V2X).In an example, a parameter may explicitly indicate that the UE iscapable of handling enhanced SPS configuration. The base station afterreceiving the UE capability message, may determine whether the UE cansupport configuration of enhanced SPS (SPS/V2X). The UE may selectivelyconfigure SPS/V2X for a UE by transmitting one or more RRC messages tothe UE.

In an example embodiment, the capability may be received on a firstsignalling bearer on the primary cell. The plurality of radio capabilityparameters may comprise a first sequence of one or more radioconfiguration parameters. A first radio configuration parameter in thefirst sequence may comprise a first parameter indicating whether SPS/V2Xmay be supported for a first band and/or first band combination. Thefirst band and/or first band combination may be in a second sequence ofone or more band combinations. The index of the first radioconfiguration parameter in the first sequence may determine the index ofthe first band combination in the second sequence.

According to some of the various embodiments, the size of the firstsequence may be the same as the size of the second sequence. The indexmay determine the order of: the first radio configuration parameter inthe first sequence; and the first band combination in the secondsequence. The first band combination may be identified by a first bandcombination parameter. The first band combination parameter may comprisea list of band identifier(s). Each of the band identifier(s) may be oneof a finite set of numbers. Each of the numbers may identify a specificband.

According to some of the various embodiments, the wireless device maysupport one or more inter-band SPS/V2Xs if the list of bandidentifier(s) includes more than one band; and the first parameterindicates that SPS/V2X is supported. In yet other embodiments, thewireless device may support multiple intra-band SPS/V2X if the list ofband identifier(s) includes one band; and the first parameter indicatesthat SPS/V2X is supported.

According to some of the various embodiments, the wireless device maynot support SPS/V2X if none of the radio configuration parameterscomprise a parameter indicating that SPS/V2X is supported.

In an example embodiment, a wireless device may transmit an RRC messagecomprising UE capability information. The UE capability information maycomprise one or more information elements comprising wireless device LTEradio capability parameters. The LTE radio capability parameters maycomprise a plurality of parameters indicating various capability of thewireless device LTE radio.

The serving base station may selectively transmit at least one secondmessage to the wireless device if the at least one parameter indicatessupport for configuration of SPS/V2X. The at least one second messagemay configure SPS/V2X in the wireless device. If the at least oneparameter does not indicate support for configuration SPS/V2X, the basestation may not configure SPS/V2X in the wireless device. If the atleast one parameter indicates support for configuration of the SPS/V2X,the base station may or may not configure SPS/V2X in the wireless devicedepending on the required wireless device configuration and many otherparameters, such as types of application running on the UE and thetraffic requirements. Transmission or not transmission (selectivetransmission) of at least one second message to configure SPS/V2X isdetermined by the base station based on many criteria described in thisspecification.

The at least one second control message may be configured to cause inthe wireless device configuration of at least one cell in the pluralityof cells and configuration of SPS/V2X. The first SPS/V2X may comprise afirst subset of the plurality of cells. The second SPS/V2X may comprisea second subset of the at least one secondary cell.

The at least one second control message may be configured to furthercause in the wireless device configuration of one or more SPSconfiguration. A cell add-modify information element may comprise afirst plurality of dedicated parameters. The first plurality ofdedicated parameters may comprise a first cell index for a firstsecondary cell in the at least one secondary cell. The at least onesecond control message may further include configuration information forphysical channels for the wireless device. The at least one secondcontrol message may be configured to further cause the wireless deviceto set up or modify at least one radio bearer.

The serving base station may receive at least one measurement reportfrom the wireless device in response to the at least one second message.The at least one measurement report may comprise signal qualityinformation of at least one of the at least one cell of at least one ofthe at least one target base station. The signal quality information maybe derived at least in part employing measurements of at least one OFDMsubcarrier. The serving base station may make a handover decision,based, at least in part, on the at least one measurement report, and/orother parameters, such as load, QoS, mobility, etc. The serving basestation may also make a decision depending on base station internalproprietary algorithm.

The serving base station may transmit at least one third message to atleast one of the at least one target base station. The at least onethird message may comprise the at least one parameter indicating whetherthe wireless device supports configuration of SPS/V2X. The at least onethird message may comprise a plurality of parameters of theconfiguration at least indicating association between at least one celland a corresponding SPS/V2X (configuration information of one or moreSPS/V2Xs). The at least one third message may be a handover requestmessage transmitted to at least one target base station to prepare thetarget base stations for the handover of the wireless device. The UEcapability parameters may be included in the at least one third message.UE dedicated radio parameters comprising UE SPS/V2X configuration mayalso be included in the handover request message. UE dedicated radioparameters may comprise MACMainconfig information element. UE dedicatedradio parameters may comprise SPS/V2X configuration including SPS/V2Xindices and associated cell indices.

According to some of the various aspects of embodiments, a serving basestation, in response to making a handover decision by the serving basestation for a wireless device, may transmit at least one third messageto at least one target base station. The at least one third message maycomprise the at least one parameter indicating whether the wirelessdevice supports configuration of SPS/V2X. The format of the parameter(information element) indicating whether the wireless device supportsconfiguration of a SPS/V2X is the same format as the UE capabilitymessage transmitted by the wireless device to the base station in thefirst message as described in the specification. The at least one thirdmessage may further comprise a plurality of parameters of theconfiguration of SPS/V2X (configuration information of SPS/V2X). Theparameters included in the configuration information of SPS/V2X may bethe same as the ones included in the at least one second message asdescribed in this specification. The at least one third message may be ahandover request message transmitted to at least one target base stationto prepare the target base stations for the handover of the wirelessdevice. The UE capability parameters may be included in the at least onethird message. UE dedicated radio parameters comprising UE SPS/V2Xconfiguration may also be included in the handover request message. UEdedicated radio parameters may comprise MACMainconfig informationelement. UE dedicated radio parameters may comprise SPS/V2Xconfiguration including SPS/V2X indices and associated cell indices.

The serving base station may receive from one of the at least one targetbase station at least one fourth message. The at least one fourthmessage may comprise configuration of a plurality of cells for thewireless device. The plurality of cells may comprise a primary cell andat least one secondary cell. The configuration may associate SPS/V2Xconfiguration with a cell in the plurality of cells.

The serving base station may transmit a fifth message to the wirelessdevice. The fifth message may comprise a plurality of parameters of theconfiguration at least indicating association between at least one celland a corresponding SPS/V2X (configuration information of SPS/V2X). Thefifth message may cause the wireless device to start a synchronizationprocess with the target base station (with a cell in the target basestation).

The base station may, before transmission of the fifth message, encryptthe fifth message and protect the fifth message by an integrity header.The fifth message may further include configuration information forphysical channels for the wireless device. The fifth message may beconfigured to cause the wireless device to set up or modify at least oneradio bearer. The fifth message may be configured to further cause thewireless device to configure at least one of a physical layer parameter,a MAC layer parameter, and an RLC layer parameter. The plurality ofcells of the target base station may be in more than one frequency band,for example, one or more cells may be in frequency band A and one ormore other cells may be in frequency band B (inter-band carrieraggregation). The wireless device may support configuration of SPS/V2X.

Example embodiments enable V2X communications in multi-carriercommunications network. In an example, a UE may be engaged in a V2Xcommunication and may utilize one or more downlink subframes to receiveeMBMS or SC-PTM signaling and/or data and one or more downlink subframesto receive unicast SPS traffic and signaling. The UE may utilize one ormore uplink/sidelink subframe to send V2X traffic, e.g. subframe withSPS allocations. When communication with multiple cells, some level ofinter-cell coordination may be performed to enable a UE to have accessto the union of downlink and uplink time resources needed for V2X whilemaintaining other communication and services through the same cell ordifferent cells.

Transmission of MBMS in E-UTRAN may use single cell point to multipointtransmission (SC-PTM) or multi-cell MBSFN transmission. In an example,the V2X server may use multipoint transmission (SC-PTM) and/ormulti-cell MBSFN to deliver V2X related information to users.

In the eMBMS system, the group data may be carried through an eMBMSsession identified by a Temporary Mobile Group Identity (TMGI) and mayinitially be forwarded to an MBMS Coordination Entity (MCE). The MCE maymulticast the data to one or more eNodeBs which may be grouped as aservice area and may be configured to serve the eMBMS session. In a PMCHsubframe, the eNodeBs may simultaneously transmit the same physicallyencoded signals according to the scheduling by the MCE. In an example,the UEs interested in the eMBMS session may attempt to combine thesignals from the eNodeBs to decode the group data. In an example, a UEwilling to access the eMBMS session may receive the group data in thePMCH. The data may be decoded based on the broadcasted information. Thegroup data in the PMCH may be scrambled with a Multimedia BroadcastSingle Frequency Network (MBSFN) area ID that can be found in SIB13. AnMBSFN area configuration message carrying the scheduling information forthe eMBMS sessions served in the cell may be also available from theMulticast Control Channel (MCCH), which may be decoded with theinformation in SIB13.

In an example, IE SystemInformationBlockType13 may contain theinformation required to acquire the MBMS control information associatedwith one or more MBSFN areas. SystemInformationBlockType13 informationelement may comprise mbsfn-AreaInfoList, and/or notificationConfig. AnotificationConfig may indicate the MBMS notification relatedconfiguration parameters. In an example, the UE may ignore this fieldwhen dl-Bandwidth included in MasterinformationBlock is set to n6.

Multi-cell transmission of MBMS may include one or more of thefollowing: Synchronous transmission of MBMS within its MBSFN Area;Combining of MBMS transmission from multiple cells may be supported.Scheduling of a MCH may be done by the MCE; A single transmission may beused for MCH (e.g., neither blind HARQ repetitions nor RLC quickrepeat); A single Transport Block may be used per TTI for MCHtransmission and the TB may use the MBSFN resources in that subframe;MTCH and MCCH may be multiplexed on the same MCH and may be mapped onMCH for p-t-m transmission; MTCH and MCCH may use the RLC-UM mode. TheMAC subheader may indicate the LCID for MTCH and MCCH; The MBSFNSynchronization Area, the MBSFN Area, and the MBSFN cells may besemi-statically configured e.g. by O&M; and/or MBSFN areas may bestatic, unless changed by O&M (e.g., no dynamic change of areas).

The SC-PTM is a type of a radio access method that may be dedicated tomulticast through the PDSCH in a single cell. In SC-PTM transmission,the UEs in a group may receive the group data through a common radioresource region in the PDSCH. The group data may be multiplexed with thenormal unicast data within a PDSCH subframe and may not cause theproblem of the radio resource granularity. The SC-PTM transmission mayutilize a group RNTI which may be allocated to a TMGI. According to thecell list given from the core network, the MCE may disseminate the groupdata to the corresponding eNodeBs. An eNodeB may transmit the group datathrough the PDSCH based on its own scheduling and may send thecorresponding DCI through the PDCCH with the group RNTI. The UEs maydecode the DCI and the group data successfully based on the pre-acquiredgroup RNTI. The UEs in a group may acquire their group RNTI from anSC-PTM configuration message, which may be periodically broadcastedthrough the Single Cell-MCCH (SC-MCCH) and may provide the mappingbetween TMGIs and group RNTIs. Since the SC-PTM may allow a UE toreceive the group data as in the PMCH case, it may require a singleradio resource allocation for disseminating the group data withoutduplicated data transmissions.

The IE SystemInformationBlockType20 may contain the information requiredto acquire the control information associated transmission of MBMS usingSC-PTM. In an example, IE SystemInformationBlockType20 may containsc-mcch-RepetionPeriod, sc-mcch-Offset, sc-mcch-FirstSubframe,sc-mcch-duration, and/or sc-mcch-ModificationPeriod. Thesc-mcch-ModificationPeriod may define periodically appearing boundaries,e.g., radio frames for which SFN mod sc-mcch-ModificationPeriod =0. Thecontents of different transmissions of SC-MCCH information may bedifferent if there is at least one such boundary in-between them. In anexample, value rf2 may correspond to 2 radio frames, value rf4 maycorrespond to 4 radio frames and so on. The sc-mcch-duration mayindicate, starting from the subframe indicated by sc-mcch-FirstSubframe,the duration in subframes during which SC-MCCH may be scheduled in PDCCHsub-frames. Absence of this IE may mean that SC-MCCH is only scheduledin the subframe indicated by sc-mcch-FirstSubframe. The sc-mcch-Offsetmay indicate, together with the sc-mcch-RepetitionPeriod, the radioframes in which SC-MCCH is scheduled e.g., SC-MCCH may be scheduled inradio frames for which: SFN mod sc-mcch-RepetitionPeriod=sc-mcch-Offset.The sc-mcch-FirstSubframe may indicate the first subframe in whichSC-MCCH is scheduled. The sc-mcch-RepetitionPeriod may define theinterval between transmissions of SC-MCCH information, in radio frames.Value rf2 may correspond to 2 radio frames, rf4 may correspond to 4radio frames and so on.

In an example, single-cell transmission of MBMS may include one or moreof the following attributes: MBMS may be transmitted in the coverage ofa single cell; One SC-MCCH and one or more SC-MTCH(s) may be mapped onDL-SCH; Scheduling may be done by the eNB; SC-MCCH and SC-MTCHtransmissions may be indicated by a logical channel specific RNTI onPDCCH (there may be a one-to-one mapping between TMGI and G-RNTI usedfor the reception of the DL-SCH to which a SC-MTCH is mapped); A singletransmission may be used for DL-SCH (e.g., neither blind HARQrepetitions nor RLC quick repeat) on which SC-MCCH or SC-MTCH is mapped;SC-MCCH and SC-MTCH may use the RLC-UM mode.

For a SC-MTCH, one or more of following scheduling information may beprovided on SC-MCCH: SC-MTCH scheduling cycle; SC-MTCH on-duration:duration in downlink subframes that the UE waits for, after waking upfrom DRX, to receive PDCCHs. If the UE successfully decodes a PDCCHindicating the DL-SCH to which this SC-MTCH is mapped, the UE may stayawake and may start the inactivity timer; SC-MTCH inactivity-timer:duration in downlink subframes that the UE waits to successfully decodea PDCCH, from the last successful decoding of a PDCCH indicating theDL-SCH to which this SC-MTCH is mapped, failing which it may re-enterDRX. The UE may restart the inactivity timer following a singlesuccessful decoding of a PDCCH.

A G-RNTI of the MAC entity may be configured by RRC with a DRXfunctionality that may control the UE's PDCCH monitoring activity forthis G-RNTI. When in RRC IDLE or RRC CONNECTED, if DRX is configured,the MAC entity may be allowed to monitor the PDCCH for this G-RNTIdiscontinuously using the DRX operation; otherwise the MAC entity maymonitor the PDCCH for this G-RNTI continuously. For a G-RNTI of the MACentity, RRC may control its DRX operation by configuring the timersonDurationTimerSCPTM, drx-InactivityTimerSCPTM, theSC-MTCH-SchedulingCycle and the value of the SC-MTCH-SchedulingOffset.The DRX operation may be performed independently for a G-RNTI andindependently from the DRX operation.

When DRX is configured for a G-RNTI, the Active Time may include thetime while onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running.When DRX is configured for a G-RNTI, the MAC entity may for a subframefor this G-RNTI start onDurationTimerSCPTM if [(SFN*10)+subframe number]modulo (SC-MTCH-SchedulingCycle)=SC-MTCH-SchedulingOffset. When DRX isconfigured for a G-RNTI, the MAC entity may for a subframe for thisG-RNTI monitor the PDCCH during the Active Time for a PDCCH-subframe andstart or restart drx-InactivityTimerSCPTM if the PDCCH indicates a DLtransmission.

With the multi-frequency deployment in LTE network, eMBMS services maybe provided on more than one frequency. In the 3GPP Rel-11, supplementswere introduced to support the continuity of eMBMS by guiding UEs tofind their interested services on other frequencies. To avoid the needfor LTE mobile devices to read the eMBMS related information onneighboring frequencies in SIB13 and MCCH message, the network mayinform the UEs which eMBMS services are provided on which frequencythrough a combination of User Service Description (USD) and SystemInformation Block Type 15 (SIB15). In the USD, a service may beassociated with its own Service Identity which may be included in theTemporary Mobile Group Identity (TMGI), the frequencies and the MBMSService Area Identities (SAIs) may belong to the MBMS service area. TheSIB15 may have a list of neighboring frequencies together with thecurrent frequency. A frequency in the list may contain a list of SAIssupported by that frequency. Combining the information in USD and SIB15,the UE may determine which frequency provides the eMBMS services it isreceiving or interested in. The information obtained from USD and SIB15may be important to the UE that is interested in receiving eMBMSservices.

The IE SystemInformationBlockType15 may contain the MBMS Service AreaIdentities (SAI) of the current and/or neighboring carrier frequencies.SystemInformationBlockType15 may comprise one of more of the followingfields: mbms-SAI-IntraFreq, mbms-SAI-InterFreqList,mbms-SAI-InterFreqList. The mbms-SAI-InterFreqList may contain a list ofneighboring frequencies including additional bands, if any, that mayprovide MBMS services and the corresponding MBMS SAIs. Thembms-SAI-IntraFreq may contain the list of MBMS SAIs for the currentfrequency. A duplicate MBMS SAI may indicate that this and followingSAIs are not offered by this cell and may be offered by neighbor cellson the current frequency. For MBMS service continuity, the UE may useMBMS SAIs listed in mbms-SAI-IntraFreq to derive the MBMS frequencies ofinterest. The mbms-SAI-List may contain a list of MBMS SAIs for aspecific frequency.

In an example, the IE SystemInformationBlockType15 may contain one ormore of the following information: multiBandInfoList, and/or InterFreq.The multiBandInfoList may be a list of additional frequency bandsapplicable for the cells participating in the MBSFN transmission. TheInterFreq may be optionally present and may need OR if thembms-SAI-InterFreqList-r11 is present. Otherwise it may not be present.

In an example, in the idle state, when a user is moving out of one cell,it may prioritize to camp to the cells on the frequencies providing itsdesired eMBMS service. In such way, the continuity of eMBMS service maybe maintained if at least one neighbor frequency provides the servicerequired by the UE. In the connected mode, besides sending themeasurement reports like in unicast transmission, the UE who may bereceiving or interested in eMBMS service may send one RRC message to theserving cell as a response to the SIB15.

MBMS Interest Indicator and may comprise of a list of frequencies onwhich the UE may be receiving or interested to receive eMBMS services.This message may contain one bit to indicate to the serving cell whetherthe UE prefers eMBMS reception to normal unicast reception. TheMBMSInterestIndication message may be used to inform E-UTRAN that the UEis receiving/interested to receive or no longer receiving/interested toreceive MBMS via an MRB or SC-MRB. mbms-FreqList may be a list of MBMSfrequencies on which the UE is receiving or interested to receive MBMSvia an MRB or SC-MRB. mbms-Priority may indicates whether the UEprioritizes MBMS reception above unicast reception. The field may bepresent (e.g., value true), if the UE prioritizes reception of listedMBMS frequencies above reception of a unicast bearers. Otherwise thefield may be absent.

In an example, the current eNB may use this information in choosing thecell to hand the UE over. The candidate cell on the frequency providingthe appropriate eMBMS services may be in first priority and when the UEswitches to this frequency, it may continue to receive its interestedservice in the target cell. With this additional enhancement, theservice continuity support for eMBMS may be improved. The UE may camp orbe handed over to the cell on the frequency that transmits the serviceit desires. In addition to use of eMBMS or SC-PTM in the downlink thesystem may configure UEs with one or more Semi-Persistent Scheduling(SPS) opportunities to send their data in the uplink or downlink. Theconfiguration of SPS parameters including the sub-frames and resourcesto be used by UE may be made so that conflicts with other transmissionand receptions in the same of different carrier is avoided.

FIG. 22 shows an example multicarrier and multi-cell operation of UEswith V2X services. A UE with V2X services may be in communication withmultiple cells at a given time. For example, UE1 may be communicatingwith Cell A as its primary cell exchanging NAS/AS signaling and userdata traffic while also communicating with Cell B for V2X traffic. In anexample, the communication of UE with Cell A and B may be on differentfrequencies, e.g. Freq. 1 and Freq. 2. In an example, eNB A may compriseone or more cells comprising Cell A. In an example, eNB B may compriseone or more cells comprising cell B. In an example, eNB A and eNB B maybe the same eNB. That is Cell A and Cell B may belong to the same eNB.

An eNB may comprise one or more cells. In this context, sometimes celland eNB terms may be used interchangeably. For example, when Cell A ofeNB A transmits a message to cell B of eNB B, the eNB A may transmit themessage to the eNB B. In an example, when a server sends a message to acell, the server sends the message to the eNB comprising the cell. Forexample, when cell A transmits a message to a UE, eNB A may transmit themessage to the UE. In an example, when cell A transmits a message to aUE, the message may be transmitted via another cell of the same eNB A tothe UE.

Based on UE capabilities, a UE may only be able to operate in one of twofrequencies F1 and F2 at a given time, which requires the serving cellsto directly or indirectly coordinate their timing and resourceconfigurations to avoid/reduce conflicting assignments to such UE. SomeUEs may also be able to concurrently operate on multiple frequencies,e.g. F1 and F2. For example the UE have carrier aggregation capabilityin which one of frequencies, e.g. F1, may be used by UE's primaryserving cell and other frequencies, e.g. F2 or F3, may be used by UEssecondary serving cells. In this case the serving Cell A may also needto know time/frequency resources configured for UE by Cell B, e.g. forV2X services, to avoid making conflicting assignments beyond UE's RFcapabilities.

The timing related parameters related to reception of eMBMS or SC-PTM indownlink of Cell B and the SPS timing parameters fortransmissions/reception of data by UE if managed by Cell B may need tobe communicated with Cell A. The same is also true for configuration oftiming resources for side-link communication by UE if configured by CellB. In the following, V2X subframes used by Cell B refer to union of MBSFN subframes used for eMBMS transmission, subframes configured forSC-PTM transmissions in Cell B. From UE perspective the V2X subframes indownlink includes Cell specific subframes used for V2X transmission ofinterest for the UE as well as subframes configured for downlink unicasttransmission based SPS configurations. In V2X subframes for uplinkinclude subframes configured for SPS transmissions by UE and thosereserved for sidelink communications.

In an example embodiment, V2X across two cells may be allowed if twocells are part of the same eNB. In an example, Cell B may be part of thesame eNB as Cell A. Cell B and Cell A are managed by collocated MACand/or RRC entities. In this example, an eNB may manage configuration oftime and resources and resource assignment to UE such that the UE cansend and receive information to Cell A and B in different subframesand/or frequencies.

In an example, a UE may not be capable of receiving signaling/traffic onCell A and V2X traffic on cell B simultaneously (e.g. in the samesubframe). The eNB (e.g. via Cell A) may transmit subframe configurationinformation to the UE informing the UE about which of the subframes areemployed by Cell A and which of the subframes are employed by Cell B forcommunications. For example, the eNB may transmit an RRC message to theUE. The message may comprise one or more parameters indicating whichsubframes are assigned to Cell A for signaling/traffic and whichsubframes are assigned to Cell B for V2X communications. For example,the eNB (e.g. via Cell A) may transmit a MAC message to the UE. Themessage may comprise one or more parameters indicating which subframesare assigned to Cell A for signaling/traffic and which subframes areassigned to Cell B for V2X communications. For example, the eNB (e.g.via Cell A) may transmit an PHY control message (e.g. DCI) to the UE.The message may comprise one or more parameters indicating whichsubframes are assigned to Cell A for signaling/traffic and whichsubframes are assigned to Cell B for V2X communications. In an example,the eNB may dynamically update the subframe configuration, e.g. when V2Xtraffic pattern changes. In an example, the allocation may not bestatic, and may be dynamically controlled by eNB, for example, bytransmitting updated control and/or scheduling messages.

In an example, Cell A and Cell B subframe configuration may beconfigured employing using a bitmap, index of preconfigured subframeconfigurations, and/or some other parameters.

Handling of concurrent V2X communication on F2 and regular networktraffic on Frequency F1 may be based on eNB implementation withoutspecific requirements on the UE.

n an example embodiment, V2X across two independent cells may be allowedif UE has two or more independent RF units which can operate ondifferent frequencies in parallel. The UE may have two or more RF radioswhich may operate in parallel. The UE may be required to use one radiofor V2X traffic and the handling of concurrent V2X communication on F2and regular network traffic on Frequency F1 may be based on UEimplementation.

In an example, a UE may transmit one or more messages to an eNB (e.g.via a serving cell) that one or more of the RF radios (e.g. frequencies,bands, etc) are engaged with other cells and/or eNBs and may not beemployed by the eNB for communication. For example, the UE may transmita message to eNB A(e.g. via Cell A) indicating that the UE istransmitting and/or receiving information (e.g. V2X) on frequency F2(from Cell B, eNB B). In an example, the UE may transmit a message to aserving eNB that the UE is engaged with communication on a first Radio.The eNB may consider this information and may not configure and/orschedule any data on the first radio.

In an example, a UE may not be able to receive signals on frequency F1and F2 simultaneously. In example UE2 which is idle mode and isinterested in V2X communication may give priority to cells with V2Xradios is its cell selection.

In an example, when a UE subscribes to V2X services, the UE may receivebands and/or frequencies employed for V2X communication, e.g. in certainarea for the application server. The UE may receive this informationfrom the application layer. The UE may prioritize the frequenciesemployed for V2X communications during the idle mode cellselection/re-selection process. The UE may select frequencies employedfor V2X so that it can receive V2X traffic.

In an example, the information about V2X services may be communicatedemploying SIB messages. For example, a field in the SIB message mayindicate whether certain frequency(ies) is employed for V2X services.The UE may prioritize the frequencies employed for V2X communicationsduring the idle mode cell selection/re-selection process. The UE mayselect frequencies employed for V2X so that it can receive V2X traffic.

In an example, during the handover process, eNB may consider theinformation on whether the target eNB supports V2X service in thehandover decision process. For example, an eNB may prioritize handoverto a target eNB that supports V2X services, over another target eNB thatdoes not support V2X service. eNBs may transmit/receive message to/fromeNBs indicating whether the eNB supports V2X services. An eNB maytransmit handover request to one or more target eNBs and receivehandover ack from the one or more target eNB. In an example, handoverrequest may request V2X services, and handover ack may includeinformation about whether the eNB supports V2X services.

In an example, a UE may transmit a message to an eNB that indicate thatthe UE is capable of and/or is interested to receive V2X services. Themessage may comprise the type of V2X services, the frequencies, andother information about the UE and the services. The eNB may use thisinformation to trigger a handover, for example, to another eNBconfigured with V2X services. In an example, the eNB may expedite thehandover process to a target eNB supporting the service.

In an example, Cell A and Cell B may be part of different eNBs but areboth in the same operator's network, e.g. in the same PLMN. In this caseCell B and Cell A may have two different MAC operations but maycoordinate some RRC configurations through X2 interface and eNBs (cells)may be connected to the same core network. In an example, UE1 mayreceive/transmit V2X traffic from/to eNB B (e.g. via Cell B) onfrequency F2 while using eNB A (e.g. via Cell A) as a primary cell onfrequency F1 for NAS/AS signaling and other data traffic. In an example,the V2X traffic may be delivered to UE from Cell B via eMBMS or SC-PTMon a Frequency F2.

In an example embodiment, the core network (e.g. MCE) or eNB B (e.g. viaCell B) configures the timing and resource configuration for V2Xtransmission to UEs independent of eNB A(e.g. for Cell A) andcommunicates such configurations via X2 interface (Option A in FIG. 23).Cell A may avoid/reduce conflicting assignments for UEs using target V2Xservices, e.g. UE1. In another example such information may be providedby the core network where MCE shares scheduling decisions on eMBMS andSC-PTM subframes also to those cells not offering these services (OptionB in FIG. 23) such as eNB A (e.g. Cell A) in this example so thatresource allocation conflicts may be avoided/reduce by eNB A(e.g. forCell A). In an example, some of the eMBMS and SC-PTM configurationparameters may be exchanged in option A and B. For example, subframeconfigurations, RB configurations, cell information, service informationand/or frequency configurations may be communicated.

The V2X resource configuration information to eNB A (e.g. for Cell A),which may be sent by V2X Server or from eNB B (e.g. Cell B), maycomprise information on subframes reserved for V2X services acrossdifferent frequencies. In an example, the V2X configuration message mayinclude frequency in which V2X is offered, in the example F2, and a bitmap showing pattern of V2X subframes reserved for V2X.

FIG. 23 shows an example multiCell V2X coordination in the same PLMN,Option A with X2 signaling and Option B with Core Network signaling. Inan example, UE1 that is connected to eNB A (e.g. Cell A) as primary cellcommunicates with eNB A (e.g. Cell A) its interest in V2X services fromeNB B (e.g. Cell B) through a V2X interest flag. This interest flag mayinclude information about which V2X services UE1 is interested and theirpriority over other services offered by eNB A (e.g. Cell A). For thisUE1 the eNB A (e.g. Cell A) may partition time resources, e.g.subframes, in downlink and/or uplink as needed, according to aconfiguration for communications with eNB A (e.g. Cell A) and accordingto another configuration for UE to communicate with eNB B (e.g. Cell B).eNB A (e.g. Cell A) may transmit a resource (frequency and/or subframe)configuration message (e.g. subframe configuration message) to the UEindicating the frame/subframe and/or frequencies of V2X service. The UEmay use this information for receiving data/traffic from eNB A (e.g.Cell A) and V2X traffic from eNB B (e.g. Cell B). Example messages areshown in FIG. 22. Messages may be transmitted in a different order asshown in FIG. 23.

In an example, the time resources in downlink may be partitioned betweeneNB A (e.g. Cell A) and eNB B (e.g. Cell B) communications with the UE,and uplink time resources may be managed and assigned by eNB A (e.g.Cell A). In this case V2X related uplink traffic may be routed througheNB A (e.g. Cell A) to V2X server. Uplink V2X traffic may be transmittedvia semi-persistent scheduling. The UE may receive configuration andgrants for uplink SPS from eNB A (e.g. Cell A). In an example, some ofthe uplink V2X traffic may be received via eNB A (e.g. Cell A) and someof the uplink V2X traffic may be transmitted via eNB B (e.g. Cell B).

In an example, where a UE may communicate with eNB B (e.g. Cell B) inuplink for V2X, the UE also includes in the V2X interest flaginformation about subframe used by UE in the uplink for V2X servicese.g. based on uplink SPS configurations by eNB B (e.g. Cell B).

In an example, for UEs which can communicate in one frequency at thetime, eNB A (e.g. Cell A) may avoid/reduce communicating with UE1 onfrequency F1 on subframes designated for V2X on Frequency F2. In anotherexample for UEs which can communicate on multiple frequencies at thesame time, e.g. for carrier aggregation, eNB A (e.g. Cell A) may takeinto account UEs engagement on Frequency F2 on V2X subframes and avoidany secondary cell time/frequency assignment which may conflict withUE1's V2X communication based on UEs capabilities. In an example,frequencies F1 and F2 may be the same frequency.

In an example, Cell B may be part of a different eNB as Cell A and alsoin a different operator's network, e.g. in the different PLMN. In thiscase Cell B and Cell A are connected to different core networks andoperate independently and may not be able to communicate via directinterface. The two cells, Cell A and B in this example, may also havedifferent timing configuration and may not be synchronized. In thisexample the information of time resources occupied by V2X services onCell B may be preconfigured and semi-static and be exchanged with eNB A(e.g. Cell A) operator in management plane (Option 1 in FIG. 24).

Given the two cells may not be synchronized, additional timing referencesynchronization information may also be included. In an example thisinformation may include current System Frame Number (SFN) and Subframe(SF) number of the coordinating cells. For example when eNB B (e.g. CellB) is used for V2X services and eNB A (e.g. Cell A) is the primary cellfor a UE, Cell B's network may inform eNB A (e.g. Cell A)'s networkthrough management plane about eNB B (e.g. Cell B)'s current SFN andSubframe number as well as patterns of subframes which are reserved forV2X communication on Frequency F2.

FIG. 24 shows an example multi-cell V2X Coordination in different PLMN,Option A with inter-PLMN management signaling and Option B with UEInterest Indication. In another example, (Option B in FIG. 24) UE1 whois receiving V2X related timing resource configuration from eNB B (e.g.Cell B) over air interface will provide eNB A (e.g. Cell A) with suchinformation e.g. through an RRC message. A new V2XInterestIndicationmessage or an extension to existing MBMSInterestIndication Message maybe used to convey this information to eNB A (e.g. Cell A).

In an example UE determines the union of time resources, e.g. subframes,which are needed for communication with eNB B (e.g. Cell B) foreMBMS/SC-PTM or SPS reception or uplink SPS transmissions, e.g. for V2Xservices of the UE. In an example the UE may communicate such subframeinformation as well as operating frequencies, in this case frequency F2,to Cell A. In an example this information may be communicated with an Nbit map for each frequency, where each bit position 1≤i≤N indicateswhether subframe i in the set is reserved for V2X, so that eNB A (e.g.Cell A) avoids/reduces use of such subframes it is resource allocationto the UE. When eNB A (e.g. Cell A) and eNB B (e.g. Cell B) are notsynchronized, e.g. there are part of different networks, the UE may alsoinclude System Frame Number (SFN) and SubFrame (SF) number of eNB B(e.g. Cell B) in V2XInterestIndication so that eNB A (e.g. Cell A) maydetermine exact timing of V2X subframes used by UE and eNB B (e.g. CellB).

In an example the V2XInterestIndication may comprise a V2X priorityflags for eNB A (e.g. Cell A) showing if UE considers some V2X trafficand communication with eNB B (e.g. Cell B) as priority over otherunicast communication with eNB A (e.g. Cell A) or not. eNB A (e.g. CellA) may avoid allocating resources to UE1 which conflicts with V2Xcommunication of UE1 and eNB B (e.g. Cell B) unless such allocations arefor services which have higher priority over V2X services based on UEpreference indicated in the V2XInterestIndication.

In example embodiments, downlink subframe configuration used for V2X,e.g. those configured for eMBMS and SC-PTM transmission, may beexchanged in the network via X2 interface and/or core network signaling.For example, downlink subframe configuration may be common acrossdifferent UEs.

Information about UE specific V2X subframes for downlink and uplink V2Xservice may be transmitted via a UE to the base station. UE specificinformation, e.g., may include SPS configurations and/or UE's prioritypreferences. A UE may transmit this information to an eNBvia anV2XinterestIndication message. V2X interest Indication may comprisesubframe configuration for UE V2X related subframes. For example, it maybe a subframe bit map for a frequency. The priority preferences mayindicate the UE priority for a service compared with other services.

In an example, UE specific signaling V2X information may be communicatedvia X2 interface between base stations. A base station may transmitinformation about V2X subframes and/SPS scheduling of one or more UEs toanother base station. The another base station may use this informationfor scheduling downlink/uplink traffic.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell 1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages. In an example, an IE may be a sequence of firstparameters (first IEs). The sequence may comprise one or more firstparameters. For example, a sequence may have a length max length (e.g.1, 2, 3, etc). A first parameter in the sequence may be identified bythe parameter index in the sequence. The sequence may be ordered.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using LAA communication systems. However, one skilled in the art willrecognize that embodiments of the disclosure may also be implemented ina system comprising one or more TDD cells (e.g. frame structure 2 and/orframe structure 1). The disclosed methods and systems may be implementedin wireless or wireline systems. The features of various embodimentspresented in this disclosure may be combined. One or many features(method or system) of one embodiment may be implemented in otherembodiments. Only a limited number of example combinations are shown toindicate to one skilled in the art the possibility of features that maybe combined in various embodiments to create enhanced transmission andreception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

1. A method comprising receiving, by a base station from a wirelessdevice, a first sequence of capability parameters each indicatingwhether a vehicle-to-everything (V2X) transmission is supported in acorresponding frequency band combination of a second sequence offrequency band combinations of the wireless device, wherein thecorresponding frequency band combination comprises one or more frequencyband identifiers each indicating a specific frequency band; andtransmitting V2X configuration parameters of a cell operating in one ofthe frequency band combinations on which the wireless device supportsthe V2X transmission.
 2. The method of claim 1, wherein the V2Xconfiguration parameters comprises: an semi-persistent scheduling (SPS)radio network temporary identifier (RNTI); at least one SPSconfiguration parameter; and an SPS configuration index for the at leastone SPS configuration parameter.
 3. The method of claim 2, furthercomprising transmitting a downlink control information (DCI)corresponding to the SPS RNTI, the DCI comprising the SPS configurationindex.
 4. The method of claim 3, wherein: the DCI indicates activationof at least one SPS configuration corresponding to the SPS configurationindex; and the DCI further comprises at least one resource parameter. 5.The method of claim 3, wherein the at least one SPS configurationparameter comprises at least one parameter indicating one or moretraffic types.
 6. The method of claim 3, wherein the DCI comprises atleast one parameter indicating one or more traffic types.
 7. The methodof claim 1, wherein an index of a first capability parameter in thefirst sequence identifies a corresponding first frequency bandcombination in the second sequence.
 8. The method of claim 1, whereinthe V2X configuration parameters are associated with sidelink SPSresources.
 9. The method of claim 1, wherein the V2X configurationparameters are associated with uplink SPS resources.
 10. The method ofclaim 2, wherein an index of a first capability parameter in the firstsequence identifies a corresponding first frequency band combination inthe second sequence.
 11. A method comprising transmitting, by a wirelessdevice to a base station, a first sequence of capability parameters eachindicating whether a vehicle-to-everything (V2X) transmission issupported in a corresponding frequency band combination of a secondsequence of frequency band combinations of the wireless device, whereinthe corresponding frequency band combination comprises one or morefrequency band identifiers each indicating a specific frequency band;and receiving V2X configuration parameters of a cell operating in one ofthe frequency band combinations on which the wireless device supportsthe V2X transmission.
 12. The method of claim 1, wherein the V2Xconfiguration parameters comprises: an semi-persistent scheduling (SPS)radio network temporary identifier (RNTI); at least one SPSconfiguration parameter; and an SPS configuration index for the at leastone SPS configuration parameter.
 13. The method of claim 2, furthercomprising receiving a downlink control information (DCI) correspondingto the SPS RNTI, the DCI comprising the SPS configuration index.
 14. Themethod of claim 3, wherein: the DCI indicates activation of at least oneSPS configuration corresponding to the SPS configuration index; and theDCI further comprises at least one resource parameter.
 15. The method ofclaim 3, wherein the at least one SPS configuration parameter comprisesat least one parameter indicating one or more traffic types.
 16. Themethod of claim 3, wherein the DCI comprises at least one parameterindicating one or more traffic types.
 17. The method of claim 1, whereinan index of a first capability parameter in the first sequenceidentifies a corresponding first frequency band combination in thesecond sequence.
 18. The method of claim 1, wherein the V2Xconfiguration parameters are associated with sidelink SPS resources. 19.The method of claim 1, wherein the V2X configuration parameters areassociated with uplink SPS resources.
 20. A system comprising: awireless device; and a base station, wherein the wireless device isconfigured to: transmit to the base station, a first sequence ofcapability parameters each indicating whether a vehicle-to-everything(V2X) transmission is supported in a corresponding frequency bandcombination of a second sequence of frequency band combinations of thewireless device, wherein the corresponding frequency band combinationcomprises one or more frequency band identifiers each indicating aspecific frequency band; and receive V2X configuration parameters of acell operating in one of the frequency band combinations on which thewireless device supports the V2X transmission; and wherein the basestation is configured to: receive the first sequence of capabilityparameters; and transmit the V2X configuration parameters.